Agoranome seller tools

Which paid offers deliver (not answering yet)

which_delivers

Read-only

Not answering yet. No seller in the deliver feed has delivery odds yet. Until it answers, a call is refused before any payment. Which paid x402 tool for this task delivers? The top five offers in a category, ranked by the lower end of each seller's 95% delivery odds (the chance it delivers at its listed terms, from paid probes, reconciled deliveries, returning buyers and settlement proofs), with price, listing and the sort key stated; sellers the odds can't tell apart rotate daily. Optional price cap. Read from Agoranome's daily deliver feed: no new spend, no model call. 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": {
      "category": "<category>"
    },
    "name": "which_delivers"
  }
}

Input Schema

Name	Required	Description
`explore`	No	Optional: give the fifth place to the most recently listed seller with an attested sample and no probe yet, labelled exploration
`category`	Yes	The task's category
`max_price`	No	Optional: only offers at or under this price per call in USD
`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.
`if_none_match`	No	Send the answer's ETag back in If-None-Match (over MCP, the if_none_match argument): while the answer is unchanged it comes back as a free 304 Not Modified.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

addedInput schema / properties / explore

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional: give the fifth place to the most recently listed seller with an attested sample and no probe yet, labelled exploration",
+  "title": "Explore"
+}

AddedNov 9, 2026

TDQS

A3.5/5.0

Behavior5/5

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

Beyond readOnly/openWorld annotations, the description discloses that it reads Agoranome's daily deliver feed with no new spend or model call, that calls are refused before payment when odds are unavailable, that failed calls are not charged, and that the $0.01 fee can be paid via x402 or a Skyfire/kya-pay token. It also explains the free 304 ETag behavior.

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

Conciseness2/5

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

The purpose is buried behind three confusing status sentences ('Not answering yet...'), and payment details are repeated. The information is useful but not front-loaded or tightly organized.

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?

For a tool with no output schema, the description explains the return set (top five offers), the ranking signal (lower bound of 95% delivery odds with its data sources), included fields (price, listing, sort key), daily rotation, and the explore option. This is enough for an agent to interpret and use the result.

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 the schema already documents category, explore, max_price, kyapay-token, and if_none_match. The description adds only a brief mention of the optional price cap and payment token, so it does not meaningfully exceed the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition eventually states it returns 'the top five offers in a category, ranked by the lower end of each seller's 95% delivery odds,' which is a clear resource and ranking method. However, it opens with 'Not answering yet' and 'No seller in the deliver feed has delivery odds yet,' which obscure whether the tool can answer at all, and it does not explicitly distinguish itself from siblings such as pick_odds or rank_check.

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?

The question 'Which paid x402 tool for this task delivers?' implies the tool is for selecting a paid offer in a category, and the price cap is described as optional. But there is no explicit when-to-use/when-not guidance or named alternative, so the agent must infer its role from context.

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.