Skip to main content
Glama

GAIP Witness Agent

by io.github.tjcgraham-rgb
OverviewDiscussionsAdmin

Extract of GAIP's record about a URL

gaip_record_extract
Read-onlyIdempotent

Use this when you need proof of what an agent or shop page declared on a date. Pass its url (optional since, until). Returns an extract of GAIP's record as kept: entries with chain positions, hashes, daily anchors and a signature. Free preview. Free, read-only, no account; inputs must be public and non-personal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe A2A agent card, MCP endpoint or shop product page URL, exactly as recorded.
limitNoOptional: most entries to return, newest kept (default 50).
sinceNoOptional: start of the range (YYYY-MM-DD or RFC 3339).
untilNoOptional: end of the range (YYYY-MM-DD, inclusive, or RFC 3339).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "since": "2026-09-01",
-    "url": "https://mcp.deepwiki.com/mcp"
-  }
-]New value: +[
+  {
+    "since": "2026-09-01",
+    "url": "https://huggingface.co/mcp"
+  }
+]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Without relying on annotations, it discloses that the tool is free, read-only, requires no account, and that inputs must be public and non-personal. It also notes it is a 'free preview', implying possible limitations. It does not describe output format details beyond listing entry fields, but that is substantial behavioral context.

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 description is compact and front-loads the primary use case, then parameters, then returns, then constraints. Every sentence adds information, though the listing of return fields and the final constraints make it slightly dense.

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 read-only lookup tool with full schema description coverage and no output schema, the description covers purpose, usage trigger, key parameters, return content, and access constraints. It is nearly complete, missing only explicit mention of the `limit` parameter and any pagination behavior.

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 coverage is 100%, so baseline is 3. The description adds value by naming the key parameters (`url`, optional `since`, `until`) and the context that the URL is an agent card, MCP endpoint, or shop product page. It omits `limit`, but the schema covers it fully.

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 states a specific verb and resource: extracting GAIP's record about a URL as proof of declaration on a date. It is clearly distinguished from siblings like gaip_evidence_pack or gaip_receipt_export by naming exactly what is returned (entries with chain positions, hashes, daily anchors, signature).

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 a clear trigger: 'Use this when you need proof of what an agent or shop page declared on a date.' This frames the use case well, but it does not name alternative sibling tools or state when not to use it.

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

All GAIP Witness Agent toolsInspect
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.

Resources