GAIP — evidence on AI agents before and after you call them

Verify a delivery or citations

gaip_verify

Use this when asked whether a service delivered what was promised or whether cited pages contain the quoted text. Pass citations, or a service url (+ checks, the result you got), or claims with observations. Returns a result per item. Free, no account; only delivery keeps a record. Inputs must be public and non-personal.

Input Schema

Name	Required	Description
`url`	No	Claims: the agent or supplier they are about. Delivery: the public https service URL that should deliver.
`checks`	No	Optional (delivery): what a good response is, e.g. [{"id": "http_status_in", "allowed": [200]}, {"id": "json_parses"}]. Default: HTTP 200 and a non-empty body.
`claims`	No	Claims to record about `url`: each a sentence or {id, text}. Each is compared with the `observations` you supply; without them it stays UNTESTED.
`result`	No	Optional (delivery): the response you received. Omitted: GAIP fetches the service URL now (public replay).
`verbose`	No	Optional: true returns the full result with every underlying field. Default: a short answer.
`metadata`	No	Optional (claims): the published agent card, MCP or OpenAPI document.
`terms_id`	No	Optional (delivery): terms_id from an earlier registration, instead of url.
`citations`	No	Citations to check: each {url, quote?} or just a URL. GAIP fetches each page once (robots.txt respected) and looks for the quote.
`keep_receipt`	No	Optional: true keeps a dated GAIP receipt of this answer and returns a continuity handle. Default: GAIP keeps no record of the task (usage is counted without its content).
`observations`	No	Optional (claims): what you saw, each {claim_id, result: PASS\|FAIL, detail}.
`continuity_handle`	No	Optional: the continuity_handle from an earlier GAIP result; links this call to your earlier ones (needed to see or remove your watches later).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

addedInput schema / properties / keep_receipt

Added value: +{
+  "default": false,
+  "description": "Optional: true keeps a dated GAIP receipt of this answer and returns a continuity handle. Default: GAIP keeps no record of the task (usage is counted without its content).",
+  "type": "boolean"
+}

Changed9 schema fields changedOct 1, 2026

changedInput schema / properties / checks / examples

Previous value: -[
-  [
-    {
-      "allowed": [
-        200
-      ],
-      "id": "http_status_in"
-    },
-    {
-      "id": "content_type_is",
-      "value": "application/json"
-    },
-    {
-      "id": "non_empty"
-    },
-    {
-      "id": "json_parses"
-    }
-  ]
-]New value: +[
+  [
+    {
+      "allowed": [
+        200
+      ],
+      "id": "http_status_in"
+    },
+    {
+      "id": "content_type_is",
+      "value": "application/json"
+    },
+    {
+      "id": "non_empty"
+    },
+    {
+      "id": "json_parses"
+    }
+  ],
+  [
+    {
+      "allowed": [
+        200
+      ],
+      "id": "http_status_in"
+    },
+    {
+      "id": "json_required_keys",
+      "keys": [
+        "status"
+      ]
+    },
+    {
+      "id": "json_path_equals",
+      "path": "status",
+      "value": "ok"
+    },
+    {
+      "id": "max_latency_ms",
+      "limit": 2000
+    }
+  ]
+]

changedInput schema / properties / checks / items / properties / id / description

Previous value: -"http_status_in (needs allowed), content_type_is (needs value), non_empty, json_parses."New value: +"http_status_in (allowed), content_type_is (value), non_empty, json_parses, json_required_keys (keys), json_path_equals (path, value), max_latency_ms (limit), max_bytes (limit), text_contains (value), regex (pattern)."

changedInput schema / properties / checks / items / properties / id / enum

Previous value: -[
-  "http_status_in",
-  "content_type_is",
-  "non_empty",
-  "json_parses"
-]New value: +[
+  "http_status_in",
+  "content_type_is",
+  "non_empty",
+  "json_parses",
+  "json_required_keys",
+  "json_path_equals",
+  "max_latency_ms",
+  "max_bytes",
+  "text_contains",
+  "regex"
+]

addedInput schema / properties / checks / items / properties / keys

Added value: +{
+  "description": "json_required_keys: top-level or dotted keys that must exist, e.g. [\"a.b\"].",
+  "items": {
+    "maxLength": 200,
+    "type": "string"
+  },
+  "maxItems": 20,
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / checks / items / properties / limit

Added value: +{
+  "description": "max_latency_ms: milliseconds (1-60000); max_bytes: body bytes (1-32768).",
+  "maximum": 60000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / checks / items / properties / path

Added value: +{
+  "description": "json_path_equals: dotted path, list items by index, e.g. items.0.id.",
+  "maxLength": 200,
+  "type": "string"
+}

addedInput schema / properties / checks / items / properties / pattern

Added value: +{
+  "description": "regex: bounded pattern searched in the body; no nested quantifiers.",
+  "maxLength": 200,
+  "type": "string"
+}

changedInput schema / properties / checks / items / properties / value / description

Previous value: -"content_type_is: the expected media type, e.g. application/json."New value: +"content_type_is: media type, e.g. application/json; text_contains: case-sensitive text; json_path_equals: the expected value (GAIP also accepts a number, boolean, null, array or object)."

changedInput schema / properties / checks / items / properties / value / maxLength
```
Previous value: -100New value: +200
```

Changed9 schema fields changedSep 30, 2026

changedInput schema / properties / checks / description

Previous value: -"Optional (delivery): what a good response is: http_status_in {allowed}, content_type_is {value}, non_empty, json_parses. Default: HTTP 200, non-empty."New value: +"Optional (delivery): what a good response is, e.g. [{\"id\": \"http_status_in\", \"allowed\": [200]}, {\"id\": \"json_parses\"}]. Default: HTTP 200 and a non-empty body."

addedInput schema / properties / checks / examples

Added value: +[
+  [
+    {
+      "allowed": [
+        200
+      ],
+      "id": "http_status_in"
+    },
+    {
+      "id": "content_type_is",
+      "value": "application/json"
+    },
+    {
+      "id": "non_empty"
+    },
+    {
+      "id": "json_parses"
+    }
+  ]
+]

addedInput schema / properties / checks / items / additionalProperties
```
Added value: +false
```

addedInput schema / properties / checks / items / properties

Added value: +{
+  "allowed": {
+    "description": "http_status_in: the acceptable HTTP statuses, e.g. [200].",
+    "items": {
+      "maximum": 599,
+      "minimum": 100,
+      "type": "integer"
+    },
+    "maxItems": 10,
+    "minItems": 1,
+    "type": "array"
+  },
+  "id": {
+    "description": "http_status_in (needs allowed), content_type_is (needs value), non_empty, json_parses.",
+    "enum": [
+      "http_status_in",
+      "content_type_is",
+      "non_empty",
+      "json_parses"
+    ],
+    "type": "string"
+  },
+  "value": {
+    "description": "content_type_is: the expected media type, e.g. application/json.",
+    "maxLength": 100,
+    "type": "string"
+  }
+}

addedInput schema / properties / checks / items / required
```
Added value: +[
+  "id"
+]
```
changedInput schema / properties / checks / maxItems
```
Previous value: -10New value: +8
```
addedInput schema / properties / checks / minItems
```
Added value: +1
```

changedInput schema / properties / claims / description

Previous value: -"Claims to compare with observations: each a sentence or {id, text}."New value: +"Claims to record about `url`: each a sentence or {id, text}. Each is compared with the `observations` you supply; without them it stays UNTESTED."

addedInput schema / properties / verbose

Added value: +{
+  "default": false,
+  "description": "Optional: true returns the full result with every underlying field. Default: a short answer.",
+  "type": "boolean"
+}

AddedSep 28, 2026

TDQS

A4/5.0

Behavior4/5

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

With annotations provided, the description still adds real context beyond them: it states the tool is free, requires no account, that only the delivery path keeps a record, and that inputs must be public and non-personal. This clarifies cost, auth, data-retention, and privacy constraints that the annotations (readOnlyHint=false, openWorldHint=true) only vaguely imply.

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

Conciseness4/5

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

The definition is compact and front-loaded: the trigger condition comes first, followed by input modes and then operational constraints. Every sentence carries weight, though the middle 'Pass ...' sentence is dense with nested parentheticals that take a moment to parse.

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, multi-mode tool with no output schema, the description covers the essential decision points: when to use it, how to select inputs, cost, and privacy limits. The one gap is the return value, described only as 'a result per item,' leaving the verdict structure unstated.

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 value by grouping the 11 parameters into three coherent usage patterns (citations / url+checks+result / claims+observations) rather than listing them. That mode-level framing helps an agent pick the right subset, which the flat schema does not convey.

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

Purpose4/5

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

The description names two concrete tasks with specific verbs and resources: verifying that a service delivered what was promised, and verifying that cited pages contain quoted text. An agent can immediately tell this is a verification tool. It does not, however, distinguish itself from siblings like gaip_check or gaip_diagnose, which would be needed for a 5.

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 opens with an explicit trigger ('Use this when asked whether...') and then maps three distinct input modes to their parameter combinations (citations; url + checks + result; claims + observations), which is genuinely actionable routing guidance. It stops short of naming when NOT to use it or pointing to alternative sibling tools.

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

All GAIP — evidence on AI agents before and after you call them tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Verify a delivery or citations

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources