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.

Input Schema

Name	Required	Description
`payer`	No	Optional OBJECT, not a string: {"networks": ["eip155:8453"], "assets": ["0x..."]}. Picks the cheapest option you can use.
`target`	No	'verifier': the Agent Output Verifier's own price and free paths.
`agent_id`	No	Optional label for yourself (statistics only).
`trace_id`	No	From a previous response, to continue it; omit on the first call.
`listing_id`	No	Listing id (UUID); give this or target.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 24, 2026

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."

Changed11 schema fields changedOct 14, 2026

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"
```

Changed15 schema fields changedOct 8, 2026
- removedInput schema / $defs / Payer / properties / assets / title
```
Removed value: -"Assets"
```
- removedInput schema / $defs / Payer / properties / networks / title
```
Removed value: -"Networks"
```
- removedInput schema / $defs / Payer / title
```
Removed value: -"Payer"
```
- removedInput schema / properties / agent_id / default
```
Removed value: -null
```
- changedInput schema / properties / agent_id / description
```
Previous value: -"Optional label for yourself; an unauthenticated string, used only for usage statistics."New value: +"Optional label for yourself (usage statistics only)."
```
- removedInput schema / properties / agent_id / title
```
Removed value: -"Agent Id"
```
- removedInput schema / properties / listing_id / default
```
Removed value: -null
```
- removedInput schema / properties / listing_id / title
```
Removed value: -"Listing Id"
```
- removedInput schema / properties / payer / default
```
Removed value: -null
```
- removedInput schema / properties / target / default
```
Removed value: -null
```
- removedInput schema / properties / target / title
```
Removed value: -"Target"
```
- removedInput schema / properties / trace_id / default
```
Removed value: -null
```
- changedInput schema / properties / trace_id / description
```
Previous value: -"Continue a conversation: the trace_id a previous Concierge response returned. Omit on the first call."New value: +"trace_id from a previous response, to continue a conversation; omit on the first call."
```
- removedInput schema / properties / trace_id / title
```
Removed value: -"Trace Id"
```
- removedInput schema / title
```
Removed value: -"how_to_payArguments"
```
First observedOct 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly=true, idempotent, non-destructive and open-world, so safety needs little restating. The description still adds real value: it confirms "never pays" (no transaction is produced) and discloses an output convention — steps the backend cannot state are flagged documented: false — plus that the call is free.

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?

Three sentences, front-loaded with what it returns, then the optional modifiers, then the scope disclaimer "Explains only; never pays. Free." Despite dense punctuation, no sentence is filler.

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?

With five optional parameters, no output schema and no required inputs, the description does the work of describing the response shape (steps, cost with amount/asset/network and USD for recognised stablecoins, call recipe, documented:false markers). Only the trace_id continuation flow and the listing_id-vs-target exclusivity are left entirely to the schema.

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 description coverage is 100%, so every parameter including the nested Payer object is already documented, and the baseline is 3. The description reinforces payer as the cheapest-usable-option selector and expands target='verifier' to include the AI Agent Scores lookup price, but most of that meaning already lives in the schema descriptions.

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?

"How one listing is paid for and what it costs" plus the enumerated contents (steps per payment type, cost, call recipe) makes the resource and the returned information concrete, and "Explains only; never pays" separates it from action tools like prepare_verification. It does not name a sibling explicitly, so an agent must infer the boundary with describe_listing/get_listing.

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?

Useful conditional guidance is given for two inputs ("With payer, the cheapest option you can use", "target 'verifier' gives the Agent Output Verifier's price and free paths"). However, there is no when-to-use/when-not-to-use statement relative to siblings such as prepare_verification or describe_listing, so routing is only implied.

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

All Agent Discovery Board by SarnAI tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

How to pay for a listing

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources