Skip to main content
Glama

E-Commerce — Refund Request Audit — Kestrel Outfitters (2b20046e)

get_agent_contract

Read-onlyIdempotent

✅ No API key needed. Fetch the hash-verifiable AgentContractV1 descriptor (version + schema_url + schema_hash) and the hosted_runtime facts — identical to /.well-known/agent.json. Fetch schema_url and match schema_hash to validate the platform contract before acting. REST twin: GET /.well-known/agent.json.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_agent_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
_rateNoOptional rating prompt on a keyed call. Absent for guests.
claim_stubNoCompact claim-stub reminder. Present only on a keyless benchmark or data rail session that holds a live stub. status is bound after a delivered birth and unbound before it.
schema_urlYes
schema_hashYes
runtime_typesYes
hosted_runtimeNo
a2awire_next_actionsNoFail-soft next-step block appended on a data rail. Absent on a benchmark rail (that rail omits the earnings feed) and when the caller is unrouted.
agent_contract_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / a2awire_next_actions / description
      Previous value: -"Fail-soft next-step block appended on a benchmark or data rail. Absent when the caller is unrouted."New value: +"Fail-soft next-step block appended on a data rail. Absent on a benchmark rail (that rail omits the earnings feed) and when the caller is unrouted."
  2. Changed3 schema fields changed
    • addedOutput schema / properties / _rate
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {
      +        "endpoint": {
      +          "type": "string"
      +        },
      +        "token": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "token",
      +        "endpoint"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Optional rating prompt on a keyed call. Absent for guests."
      +}
    • addedOutput schema / properties / a2awire_next_actions
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Fail-soft next-step block appended on a benchmark or data rail. Absent when the caller is unrouted."
      +}
    • addedOutput schema / properties / claim_stub
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {
      +        "balance": {
      +          "type": "integer"
      +        },
      +        "cap": {
      +          "type": "integer"
      +        },
      +        "expires_at": {
      +          "type": "string"
      +        },
      +        "status": {
      +          "enum": [
      +            "bound",
      +            "unbound"
      +          ],
      +          "type": "string"
      +        },
      +        "to_bind": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "door": {
      +              "type": "string"
      +            },
      +            "field": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Compact claim-stub reminder. Present only on a keyless benchmark or data rail session that holds a live stub. status is bound after a delivered birth and unbound before it."
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new context: no API key is required, the response is identical to the /.well-known/agent.json endpoint, and the payload is hash-verifiable — useful for an agent reasoning about auth and trust.

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?

Auth note is front-loaded and the validation instruction follows immediately, so the important part lands first. Minor waste: 'identical to /.well-known/agent.json' and 'REST twin: GET /.well-known/agent.json' state the same fact twice.

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 no-argument, read-only descriptor fetch with a declared output schema, this covers purpose, auth, validation workflow and REST equivalence — enough to call it correctly. The only remaining gap is routing relative to verify_contract.

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?

Zero-parameter tool, so the baseline is 4. The description reinforces that no arguments are needed (no API key, no owner parameter) and the schema already notes the owner is derived from the authenticated principal, leaving no ambiguity about invocation.

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?

Names a specific verb and resource ('Fetch the hash-verifiable AgentContractV1 descriptor') and enumerates the exact payload fields (version, schema_url, schema_hash, hosted_runtime facts). It stops short of differentiating itself from the sibling verify_contract, so the agent must still infer which of the two to call for validation.

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 explicit sequencing guidance — 'Fetch schema_url and match schema_hash to validate the platform contract before acting' — which tells the agent both when to call it and what to do with the result. It does not name an alternative tool or state when not to use it, which keeps this below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources