Agoranome seller tools

Pre-flight plan quote

plan_quote

Read-only

Use when a buyer's planner agent is about to start a batch of paid x402 calls: post a plan of seller URLs and call counts and get the total cost, each seller's listing and certification state, its expected failure share from reconciled receipts, the fit against your caps (per call, per seller, total, policy tier), and every certified seller in the same category sorted by price with the sort key stated. Price: $0.01 in USDC per call, paid with x402 inside the tool call. Or send a Skyfire pay or kya-pay token in the kyapay-token header (or in this tool's kyapay-token argument), and this tool charges $0.01 to it. Failed calls aren't charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plan": "<plan>"
    },
    "name": "plan_quote"
  }
}

Input Schema

Name	Required	Description
`caps`	No	max_price_usd, max_per_seller_usd, max_total_usd, tier
`plan`	Yes	Lines of {seller: URL, calls: n}
`kyapay-token`	No	A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

addedInput schema / properties / kyapay-token

Added value: +{
+  "description": "A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.",
+  "type": "string"
+}

AddedOct 26, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the $0.01 per-call USDC charge, that payment happens via x402 inside the call, the two alternate auth paths (Skyfire pay or kya-pay token via header or argument), and that failed calls are not charged. Those cost and failure-billing semantics are the exact things an agent needs before committing a planner to a batch. Note a mild tension with readOnlyHint, but the hint concerns data mutation, not payment, and the description is explicit about the charge.

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?

Front-loaded with the 'Use when' trigger and then the return contents, with pricing and auth pushed to the end where they belong. It is one dense paragraph and the payment sentences are long, but every clause carries information an agent would otherwise have to discover by trial.

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?

There is no output schema, so the description carries the return-value burden and does so by enumerating each returned element including the sort key for alternatives. Combined with pricing, failure-billing, and both auth paths, an agent has everything needed to invoke this correctly on the first try.

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; the description still adds meaning by spelling out the four cap dimensions (per call, per seller, total, policy tier) as a coherent set and by explaining that the kyapay-token argument is the fallback for clients that cannot set the header. It does not explain the plan line format beyond what the schema states, so it sits just above baseline.

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?

States a specific verb and resource ('post a plan of seller URLs and call counts') and enumerates the concrete outputs: total cost, per-seller listing/certification state, expected failure share, cap fit, and same-category alternatives sorted by price. An agent knows exactly what it gets back. It does not name a sibling it replaces or is replaced by, which keeps it from a 5.

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?

The trigger is explicit and situational: 'Use when a buyer's planner agent is about to start a batch of paid x402 calls.' That is a clear pre-flight context, but there is no when-not guidance and no named alternative (e.g., a single-call check among the sibling tools) for the one-off case.

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

All Agoranome seller tools tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.