GAIP Procurement Evidence Agent

Verify an agent's or supplier's claims

gaip_verify_supplier_claims

Use this to check what an agent, API or supplier claims. Pass claims (each with an id; add check_url and GAIP tests it now), your observations and metadata. Returns per claim what GAIP saw, what you reported and whether they agree. Free, no account; records a GAIP receipt only. Inputs must be public and non-personal.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`claims`	Yes	Claims to check, each {id, text}.
`metadata`	Yes	The published agent card, MCP server description or OpenAPI document (as JSON).
`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_claim_check
`observations`	No	Optional: what you saw, each {claim_id, result: PASS\|FAIL, detail}.
`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.

Changed9 schema fields changedSep 28, 2026

addedInput schema / properties / claims / description
```
Added value: +"Claims to check, each {id, text}."
```

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 / 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 / metadata / description

Added value: +"The published agent card, MCP server description or OpenAPI document (as JSON)."

addedInput schema / properties / observations / description

Added value: +"Optional: what you saw, each {claim_id, result: PASS|FAIL, detail}."

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: +[
+  {
+    "claims": [
+      {
+        "id": "c1",
+        "text": "Returns JSON forecasts over MCP"
+      },
+      {
+        "id": "c2",
+        "text": "Responds within 2 seconds"
+      }
+    ],
+    "counterparty_id": "example-weather-agent",
+    "metadata": {
+      "protocolVersion": "2025-06-18",
+      "url": "https://weather.example.com/mcp"
+    },
+    "observations": [
+      {
+        "claim_id": "c1",
+        "detail": "tools/call returned valid JSON",
+        "result": "PASS"
+      },
+      {
+        "claim_id": "c2",
+        "detail": "p95 latency 4.8 s over 20 calls",
+        "result": "FAIL"
+      }
+    ]
+  }
+]

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_claim_check"
```

changedInput schema / required

Previous value: -[
-  "data_classification",
-  "counterparty_id",
-  "task_class",
-  "protocol",
-  "claims",
-  "metadata"
-]New value: +[
+  "claims",
+  "metadata"
+]

First observedSep 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, and the description usefully adds what the write actually is ('records a GAIP receipt only') plus cost/auth context ('Free, no account'). With no output schema, it also discloses the return shape (per-claim what GAIP saw, what you reported, whether they agree), which is the right burden to carry.

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 with the core action front-loaded, then inputs, then return shape, then constraints. No filler or restated name/title content.

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 an 11-parameter, nested-object tool with no output schema, the description covers the meaning of the main flow, the optional live-test path, and the return semantics. Secondary params (episode_id, task_class, continuity_handle, synthetic) are left to the schema, which documents them adequately, so completeness is solid though not exhaustive.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains the claim object's id requirement and the non-schema `check_url` field that triggers immediate GAIP testing, and clarifies that observations are your reported results versus GAIP's own findings. That earns above baseline.

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?

States a specific verb+resource ('check what an agent, API or supplier claims') and spells out the core mechanic (pass claims, optionally add check_url for GAIP to test live, supply observations). There are no siblings to distinguish from, and the scope is unambiguous.

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?

Gives clear when-to-use context ('Use this to check what an agent, API or supplier claims') plus a hard precondition ('Inputs must be public and non-personal'), and notes it is free with no account required. It stops short of explicit when-not-to-use guidance, but with no sibling tools the practical gap is small.

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

All GAIP Procurement Evidence Agent tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Verify an agent's or supplier's claims

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources