Skip to main content
Glama

GAIP Witness Agent

by io.github.tjcgraham-rgb
OverviewDiscussionsAdmin

Export a delivery evidence bundle

witness_dispute_bundle
Read-onlyIdempotent

Use this when a witnessed delivery failed and you must hand the facts to the other party or a resolver. Pass terms_id or a delivery receipt_id. Returns one hash-stamped bundle: terms, every check, receipts, timeline, summary. No judgement of who is right. Free, read-only, no account; inputs must be public and non-personal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
terms_idNoOr the terms_id (wt_...) of the agreement.
receipt_idNoA delivery receipt_id from witness_delivery.
receipt_formatNogaip (default) or x402_sar: also give each delivery in the x402 SAR draft shape.gaip
continuity_handleNoOptional: the continuity_handle that registered a DELIVERY_SLA watch on these terms; adds your SLA breaches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / continuity_handle
      Added value: +{
+  "description": "Optional: the continuity_handle that registered a DELIVERY_SLA watch on these terms; adds your SLA breaches.",
+  "type": "object"
+}
    • addedInput schema / properties / receipt_format
      Added value: +{
+  "default": "gaip",
+  "description": "gaip (default) or x402_sar: also give each delivery in the x402 SAR draft shape.",
+  "enum": [
+    "gaip",
+    "x402_sar"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / receipt_id / description
      Previous value: -"A receipt_id returned by an earlier GAIP call."New value: +"A delivery receipt_id from witness_delivery."
    • addedInput schema / properties / terms_id
      Added value: +{
+  "description": "Or the terms_id (wt_...) of the agreement.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "receipt_id"
-]
  2. Changed1 schema field changed
    • addedInput schema / properties / receipt_id / description
      Added value: +"A receipt_id returned by an earlier GAIP call."
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive. The description adds genuinely new context: it is free, needs no account, requires public and non-personal inputs, and makes 'no judgement of who is right' explicit. That is useful beyond the structured hints.

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 trigger, then the input choice, then what is returned, then constraints. Every sentence earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 explicitly enumerates the returned bundle contents and states the access/cost constraints, so an agent has everything needed to call it and understand the result.

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 the baseline is 3, but the description adds the one-of selection rule ('Pass terms_id or a delivery receipt_id') that the schema (0 required params, no oneOf) does not encode, clarifying how to satisfy the input.

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 (export/hand over) and resource (a hash-stamped delivery evidence bundle containing terms, checks, receipts, timeline, summary), and its 'delivery failed / dispute' framing separates it from siblings like witness_delivery and gaip_receipt_export.

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?

Opens with an explicit trigger: 'Use this when a witnessed delivery failed and you must hand the facts to the other party or a resolver.' Clear context for invocation, though it does not name alternative siblings 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