Skip to main content
Glama

An agent's record

agent_record
Read-onlyIdempotent

Use this for one ranked agent's full free record; to look up one or many agents by id, name or wallet, use find_agent. The free record of one ranked agent: rank with evidence, bindings, and its 25 newest payments with counterparties. Unranked ids return not found: an agent never seen paying has no record to sell or show.

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": "agent_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoToken id, slug or wallet address (required; agent is accepted as the same field)
agentNoSame as id

Output Schema

NameRequiredDescriptionDefault
urlNo
noteNo
agentNoThe record: rank with evidence, bindings, the 25 newest payments
as_ofNo
rankedNofalse when the id is not among ranked agents

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / agent
      Added value: +{
      +  "description": "Same as id",
      +  "type": "string"
      +}
    • changedInput schema / properties / id / description
      Previous value: -"Token id, slug or wallet address"New value: +"Token id, slug or wallet address (required; agent is accepted as the same field)"
    • removedInput schema / required
      Removed value: -[
      -  "id"
      -]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "agent": {
      +      "description": "The record: rank with evidence, bindings, the 25 newest payments",
      +      "type": "object"
      +    },
      +    "as_of": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "ranked": {
      +      "description": "false when the id is not among ranked agents",
      +      "type": "boolean"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavior on top: the payments section is capped at the 25 newest, and unranked ids fail with not found rather than returning an empty record. The only gap is the unexplained word 'free', which hints at a paid/full variant without describing what differs.

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 first clause front-loads the use case and the alternative, followed by content scope and the failure case — a good ordering. There is mild repetition in saying 'full free record' and then restating 'The free record of one ranked agent' in the next clause.

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?

An output schema exists, so return shape need not be explained, and the description still covers scope, the payment cap, and the not-found case. It leaves the free/paid distinction implicit, which is a small but real ambiguity for a tool whose value proposition hinges on that boundary.

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%, so the id/agent alias and accepted formats (token id, slug, wallet address) are already documented in structured fields. The description adds nothing about the parameters themselves, so the 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?

States a specific verb and resource: fetch the full free record of one ranked agent, and enumerates its contents (rank with evidence, bindings, 25 newest payments with counterparties). It also names the sibling it is not (find_agent) for lookup by id/name/wallet, so an agent can pick between them without opening either schema.

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?

Gives explicit routing: this tool for one ranked agent's full record, find_agent for looking up one or many agents by id, name or wallet. It also states the exclusion condition — unranked ids return not found, since an agent never seen paying has no record — which is exactly the when-not guidance an agent needs.

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.