GAIP Integration & Protocol Agent

Check an AI agent or MCP server

check_agent_conformance

Read-onlyIdempotent

Use this when asked to check an AI agent or MCP server: does it work, is it reachable, is its card valid ("check this agent", "is this MCP server up?"). Pass just its url. Returns READY / FIXES_NEEDED / NO_AGENT_CARD / UNREACHABLE with fixes and a receipt. Free, read-only, no account; inputs must be public and non-personal.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No	Public https link to an agent, its A2A agent card, MCP server description or OpenAPI document. GAIP fetches, validates and reach-tests it. Use instead of metadata.
`mode`	No	CONFORMANCE (default) checks the interface; VERIFY_BEFORE_CALL returns task-specific evidence about `target` for `intended_task`.
`target`	No	VERIFY_BEFORE_CALL: the counterparty URL or reference.
`metadata`	No	Alternative to url: the agent card or MCP/OpenAPI document itself.
`protocol`	No	Counterparty protocol. Inferred from metadata when omitted, otherwise MCP.
`source_url`	No	Optional: where `metadata` was published, used only to resolve relative endpoints. Never fetched.
`intended_task`	No	VERIFY_BEFORE_CALL: what you intend to delegate.
`declared_identity`	No	Optional: the name the agent claims.
`expected_endpoint`	No	Optional: the endpoint you expect; a different primary endpoint is reported as ENDPOINT_DRIFT.
`data_classification`	No	PUBLIC (default) or NON_PERSONAL_PUBLIC. Never send personal data.	PUBLIC

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 28, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "metadata": {
-      "name": "GAIP Broker",
-      "protocolVersion": "2025-06-18",
-      "tools": [],
-      "url": "https://www.gaipagents.com/mcp"
-    }
-  }
-]New value: +[
+  {
+    "url": "https://www.gaipagents.com/.well-known/agent-card.json"
+  },
+  {
+    "metadata": {
+      "name": "GAIP Broker",
+      "protocolVersion": "2025-06-18",
+      "tools": [],
+      "url": "https://www.gaipagents.com/mcp"
+    }
+  }
+]

addedInput schema / properties / data_classification / description

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

addedInput schema / properties / declared_identity / description
```
Added value: +"Optional: the name the agent claims."
```

addedInput schema / properties / intended_task / description

Added value: +"VERIFY_BEFORE_CALL: what you intend to delegate."

addedInput schema / properties / metadata / description

Added value: +"Alternative to url: the agent card or MCP/OpenAPI document itself."

addedInput schema / properties / mode / description

Added value: +"CONFORMANCE (default) checks the interface; VERIFY_BEFORE_CALL returns task-specific evidence about `target` for `intended_task`."

addedInput schema / properties / target / description

Added value: +"VERIFY_BEFORE_CALL: the counterparty URL or reference."

Changed5 schema fields changedSep 28, 2026

addedInput schema / examples

Added value: +[
+  {
+    "metadata": {
+      "name": "GAIP Broker",
+      "protocolVersion": "2025-06-18",
+      "tools": [],
+      "url": "https://www.gaipagents.com/mcp"
+    }
+  }
+]

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

addedInput schema / properties / expected_endpoint

Added value: +{
+  "description": "Optional: the endpoint you expect; a different primary endpoint is reported as ENDPOINT_DRIFT.",
+  "format": "uri",
+  "type": "string"
+}

addedInput schema / properties / protocol / description

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

addedInput schema / properties / source_url

Added value: +{
+  "description": "Optional: where `metadata` was published, used only to resolve relative endpoints. Never fetched.",
+  "format": "uri",
+  "maxLength": 2048,
+  "type": "string"
+}

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / url

Added value: +{
+  "description": "Public https link to an agent, its A2A agent card, MCP server description or OpenAPI document. GAIP fetches, validates and reach-tests it. Use instead of metadata.",
+  "format": "uri",
+  "maxLength": 2048,
+  "type": "string"
+}

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 already cover readOnly/idempotent/non-destructive/open-world, so the bar is lower. The description adds real context: it's free, no account required, inputs must be public and non-personal, and it returns fixes plus a receipt. It doesn't explain what happens on fetch failure vs validation failure in depth, but it discloses the safety and side-effect profile well.

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?

Front-loaded with the use case, then invocation guidance, then return values and constraints — all in roughly three dense, high-value sentences with no filler.

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 no output schema, it covers purpose, trigger, return states, and constraints. It could say more about the VERIFY_BEFORE_CALL mode and the receipt, but the schema descriptions fill most of that gap and nothing critical is missing from the description itself.

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 coverage is 100% and each of the 10 parameters has its own description, so the schema already carries parameter semantics. The description only mentions url and reinforces the public/non-personal constraint; it adds little beyond the schema. 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 names a specific verb+resource ('check an AI agent or MCP server'), states the questions it answers ('does it work, is it reachable, is its card valid'), and enumerates the exact return states. This clearly distinguishes it from siblings like gaip_observatory_lookup or the gaip_watch_* family.

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

Usage Guidelines5/5

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

It gives explicit trigger phrases ('check this agent', 'is this MCP server up?') and instructs 'Pass just its url', plus constraints (inputs must be public and non-personal). This tells the agent both when to use and how to invoke it.

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

All GAIP Integration & Protocol Agent tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Check an AI agent or MCP server

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources