Skip to main content
Keep a small set of contract checks in your integration so an added field or a changed deployment does not silently change a report.

​
Discover the current contract

Refresh the MCP tool catalog when connecting or updating a client. Validate outgoing names and types against inputSchema. This documentation edition covers 43 tools from the reviewed Dev source. Deployment catalogs can differ, so a count is not a capability guarantee. Treat project IDs and run IDs as strings, tolerate added response fields, and preserve nulls. Validate units and response scope before formatting values. Do not infer metric meaning from a field name shared by another API. schema_version: "1.0" is the measurement envelope’s version label. It is separate from the negotiated MCP protocol version, the host application’s version, and an IQRush release number.

​
Known differences in this edition

​
Check a release with representative cases

Use a project you are authorized to read. Confirm project discovery, a ready run, one measurement with a confidence interval, one grouped result, an empty or unavailable result, and any comparison your application relies on. Compare matching run IDs and scopes before comparing the UI with a connector result. If two interfaces disagree, preserve both responses and their exact scopes for investigation. Do not quietly average them or choose whichever result better supports the report. Next: Availability and limits.