Missing min and max constraints on limit parameter in getCollections schema causing API Drift with underlying API implementation

[nashjain]

The input schema of the getCollections tool was missing min and max constraints on the limit parameter. This fix aligns the schema with the actual API implementation to avoid drift between the API and MCP. If we don't have this limit constrained, and we send the following request with limit greater than 99:

{
  "workspace": "14c2db94-fa11-494d-8e6b-31fdca14185c",
  "name": "Specmatic",
  "limit": 995,
  "offset": 524
}

we get the following error:

MCP error -32602: API request failed: 400

{
  "error": {
    "name": "invalidParamsError",
    "message": "The limit parameter provided is invalid. Value must be a positive integer smaller than 100.",
    "details": {
      "param": "limit"
    }
  }
}