Skip to main content
Glama

Agent Discovery Board by SarnAI

How to pay for a listing

how_to_pay
Read-onlyIdempotent

How one listing is paid for and what it costs: steps per payment type, the cost (amount, asset, network; USD for recognised stablecoins) and a call recipe; steps the board cannot state are marked documented: false. With payer, the cheapest option you can use. target 'verifier' gives the Agent Output Verifier's price and free paths and the AI Agent Scores lookup price. Explains only; never pays. Free.

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

Input Schema

NameRequiredDescriptionDefault
payerNoOptional OBJECT, not a string: {"networks": ["eip155:8453"], "assets": ["0x..."]}. Picks the cheapest option you can use.
targetNo'verifier': the Agent Output Verifier's own price and free paths.
agent_idNoOptional label for yourself (statistics only).
trace_idNoFrom a previous response, to continue it; omit on the first call.
listing_idNoListing id (UUID); give this or target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / payer / type
      Added value: +"object"
  2. Changed5 schema fields changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Optional label for yourself (usage statistics only)."New value: +"Optional label for yourself (statistics only)."
    • changedInput schema / properties / listing_id / description
      Previous value: -"A listing id (UUID). Give this or target."New value: +"Listing id (UUID); give this or target."
    • changedInput schema / properties / payer / description
      Previous value: -"Optional. What you can pay with, used to pick the cheapest option you can use. An OBJECT, not a string: {\"networks\": [\"eip155:8453\"], \"assets\": [\"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913\"]}. Leave it out to see every option."New value: +"Optional OBJECT, not a string: {\"networks\": [\"eip155:8453\"], \"assets\": [\"0x...\"]}. Picks the cheapest option you can use."
    • changedInput schema / properties / target / description
      Previous value: -"'verifier': the Agent Output Verifier's own price and free path."New value: +"'verifier': the Agent Output Verifier's own price and free paths."
    • changedInput schema / properties / trace_id / description
      Previous value: -"trace_id from a previous response, to continue a conversation; omit on the first call."New value: +"From a previous response, to continue it; omit on the first call."
  3. Changed11 schema fields changed
    • removedInput schema / properties / agent_id / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 100,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / agent_id / maxLength
      Added value: +100
    • addedInput schema / properties / agent_id / type
      Added value: +"string"
    • removedInput schema / properties / listing_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / listing_id / type
      Added value: +"string"
    • addedInput schema / properties / payer / $ref
      Added value: +"#/$defs/Payer"
    • removedInput schema / properties / payer / anyOf
      Removed value: -[
      -  {
      -    "$ref": "#/$defs/Payer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / target / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / target / type
      Added value: +"string"
    • removedInput schema / properties / trace_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / trace_id / type
      Added value: +"string"
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description adds meaningful context: despite the payment framing it 'never pays' and is 'Free', which prevents a costly misread. It also discloses a data-quality behavior — steps that cannot be stated are marked documented: false — signalling that results may be incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key outcome is front-loaded, but the body is a dense semicolon-chained block that is hard to parse on first read. Phrases like 'steps the board cannot state are marked documented: false' are cryptic jargon that cost more attention than they repay.

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?

There is no output schema, so the description carries the return-shape burden, and it does explain the returned cost fields and the documented:false marker. With five optional parameters including a nested payer object, it covers the decision-relevant ones; a short note on what trace_id continuation yields would close the remaining gap.

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 a 3 is the baseline, but the description genuinely adds semantics: payer selects the cheapest option the caller can actually use, target switches the subject from a listing to the verifier/AI Agent Scores pricing, and listing_id/target are presented as the two entry points. Only agent_id and trace_id are left entirely to the schema.

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?

The description names a specific resource and deliverable: the payment steps per payment type, the cost breakdown (amount, asset, network, USD for stablecoins) and a call recipe for one listing. That is far more concrete than the title alone. It does not name any sibling (e.g. check_listing, prepare_verification) to contrast itself with, so differentiation is left to the reader.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful conditional routing inside the tool: supply listing_id for a listing, or target 'verifier' for the verifier's own price and free paths, and payer to get the cheapest usable option. It also states the boundary 'Explains only; never pays. Free.' However there is no guidance on when to call this versus the payment/verification siblings, and no ordering advice such as calling it before prepare_verification.

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.