GAIP Supplier Watch Agent

What changed between two versions

gaip_compare_supplier_snapshots

Use this when asked what changed between two versions of an agent card, MCP server description or OpenAPI document ("did this API break?"). Pass prior and current. Returns each change as BREAKING / NON_BREAKING / INFO with migration notes and a receipt. Free, no account; records a GAIP receipt only. Inputs must be public and non-personal.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`prior`	Yes	The earlier version: agent card, MCP server description, OpenAPI document or snapshot.
`current`	Yes	The later version, same kind as `prior`.
`protocol`	No	Counterparty protocol. Inferred from metadata when omitted, otherwise MCP.
`synthetic`	No	Optional: true marks a test call.
`episode_id`	No	Optional: your own id to group related calls.
`task_class`	No	Optional: short name of the task, e.g. weather_forecast.	supplier_snapshot_comparison
`counterparty_id`	No	Name or URL of the agent/service. Optional.
`continuity_handle`	No	Optional: the continuity_handle from an earlier GAIP result; links this call to your earlier ones.
`data_classification`	No	PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data.	PUBLIC
`independent_operator_id`	No	Optional: your operator id (recorded as a claim, not verified).

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 28, 2026

addedInput schema / properties / continuity_handle / description

Added value: +"Optional: the continuity_handle from an earlier GAIP result; links this call to your earlier ones."

addedInput schema / properties / current / description

Added value: +"The later version, same kind as `prior`."

addedInput schema / properties / data_classification / description

Added value: +"PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data."

addedInput schema / properties / episode_id / description

Added value: +"Optional: your own id to group related calls."

addedInput schema / properties / independent_operator_id / description

Added value: +"Optional: your operator id (recorded as a claim, not verified)."

addedInput schema / properties / prior / description

Added value: +"The earlier version: agent card, MCP server description, OpenAPI document or snapshot."

addedInput schema / properties / synthetic / description
```
Added value: +"Optional: true marks a test call."
```

addedInput schema / properties / task_class / description

Added value: +"Optional: short name of the task, e.g. weather_forecast."

Changed6 schema fields changedSep 28, 2026

addedInput schema / examples

Added value: +[
+  {
+    "counterparty_id": "example-weather-agent",
+    "current": {
+      "capabilities": {
+        "streaming": true
+      },
+      "name": "Weather Agent",
+      "protocolVersion": "0.3.0",
+      "security": [
+        {
+          "bearer": []
+        }
+      ],
+      "securitySchemes": {
+        "bearer": {
+          "scheme": "bearer",
+          "type": "http"
+        }
+      },
+      "skills": [
+        {
+          "id": "forecast",
+          "name": "Forecast"
+        }
+      ],
+      "url": "https://weather.example.com/v2/a2a",
+      "version": "2.0.0"
+    },
+    "prior": {
+      "capabilities": {
+        "streaming": true
+      },
+      "name": "Weather Agent",
+      "protocolVersion": "0.3.0",
+      "skills": [
+        {
+          "id": "forecast",
+          "name": "Forecast"
+        },
+        {
+          "id": "alerts",
+          "name": "Severe weather alerts"
+        }
+      ],
+      "url": "https://weather.example.com/a2a",
+      "version": "1.4.0"
+    }
+  }
+]

addedInput schema / properties / counterparty_id / description

Added value: +"Name or URL of the agent/service. Optional."

addedInput schema / properties / data_classification / default
```
Added value: +"PUBLIC"
```

addedInput schema / properties / protocol / description

Added value: +"Counterparty protocol. Inferred from metadata when omitted, otherwise MCP."

addedInput schema / properties / task_class / default
```
Added value: +"supplier_snapshot_comparison"
```

changedInput schema / required

Previous value: -[
-  "data_classification",
-  "counterparty_id",
-  "task_class",
-  "protocol",
-  "prior",
-  "current"
-]New value: +[
+  "prior",
+  "current"
+]

First observedSep 27, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With readOnlyHint=false, the description usefully explains the side effect ('records a GAIP receipt only') and adds cost/auth context ('Free, no account') plus a data constraint ('inputs must be public and non-personal'). It also pre-announces the return taxonomy (BREAKING/NON_BREAKING/INFO with migration notes). It stops short of disclosing failure modes or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with the trigger and naming the required params, then output shape, then cost/constraint caveats. Every sentence carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter tool with nested objects and no output schema, the description covers the trigger, required inputs, return classification and side effects/constraints. The optional GAIP plumbing parameters (continuity_handle, episode_id, etc.) are left to the schema, which is acceptable given full coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all 10 parameters including enums and nested objects. The description only names `prior` and `current`, adding nothing the schema does not already provide; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb (compare/what changed) with the exact resource set (agent card, MCP server description, OpenAPI document) and gives a plain-language trigger ('did this API break?'). An agent can distinguish this from generic change tools such as gaip_manifest_changes without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-to-use condition ('Use this when asked what changed between two versions') and the required inputs. It does not name or exclude sibling alternatives, so it falls short of a full routing rule but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GAIP Supplier Watch Agent tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

What changed between two versions

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources