Skip to main content
Glama

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

by io.github.tjcgraham-rgb
OverviewDiscussionsAdmin

Check an AI agent, MCP server or API

gaip_check
Read-onlyIdempotent

Use this when asked whether an AI agent, MCP server or API works or has changed, e.g. before adding or paying it. Pass its url. Returns a verdict, fixes, dated history when observed, and a receipt. With agent (e.g. GPTBot): may your bot fetch it (robots.txt, AI-crawler rules)? Free, read-only, no account; inputs must be public and non-personal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic https link to the agent, its A2A agent card, MCP server endpoint or OpenAPI document. GAIP fetches, validates and reach-tests it; an MCP endpoint gets a read-only handshake (initialize, tools/list).
agentNoOptional: ask "may my agent fetch this url?" instead. Your agent's user-agent token, e.g. GPTBot; GAIP reads the site's robots.txt and AI-permission files (gaip_check_permission).
verboseNoOptional: true returns the full result with every underlying field. Default: a short answer.
intended_taskNoOptional: what you plan to hand it, e.g. 'weather forecast for London'. Adds task-specific evidence.
continuity_handleNoOptional: 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.

  1. Changed1 schema field changed
    • addedInput schema / properties / agent
      Added value: +{
+  "description": "Optional: ask \"may my agent fetch this url?\" instead. Your agent's user-agent token, e.g. GPTBot; GAIP reads the site's robots.txt and AI-permission files (gaip_check_permission).",
+  "maxLength": 300,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Public https link to the agent, its A2A agent card, MCP server endpoint or OpenAPI document. GAIP fetches, validates and reach-tests it."New value: +"Public https link to the agent, its A2A agent card, MCP server endpoint or OpenAPI document. GAIP fetches, validates and reach-tests it; an MCP endpoint gets a read-only handshake (initialize, tools/list)."
  3. Changed1 schema field changed
    • 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"
+}
  4. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety bar is partly met. The description adds genuinely useful context beyond them: free, no account required, inputs must be public and non-personal, and it discloses the return contents (verdict, fixes, dated history, receipt).

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?

Front-loaded with the trigger condition, then the required input, then the return summary and the agent mode. Dense and largely waste-free, though the parenthetical robots.txt/AI-crawler detail is slightly redundant with the schema.

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?

With no output schema, the description carries the burden of describing returns and does so (verdict, fixes, dated history, receipt). A 5-param tool with a nested object is otherwise covered by the schema; only the absence of any sibling differentiation keeps this from being complete.

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 already documents url, agent, verbose, intended_task and continuity_handle in detail. The description only restates url and the agent mode, adding little syntax or format meaning beyond the schema — the baseline 3 applies.

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?

States a specific verb and resource: checks whether an AI agent, MCP server or API works or has changed. An agent can tell this is a health/change-verification tool, though it never names or contrasts itself with the siblings gaip_diagnose, gaip_verify or gaip_watch.

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 an explicit trigger ("Use this when asked whether ... works or has changed, e.g. before adding or paying it") and a second mode via the `agent` parameter. No when-not guidance and no routing to the sibling tools, so it falls short of a 5.

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 toolsInspect
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.

Resources