Skip to main content
Glama

Agoranome buyer checks and market data

Fair Offer check (free)

check_fair_offer
Read-only

Free: check any x402 offer's Fair Offer block from outside, without paying. Each of the eight Fair Offer rules comes back verified, declared, contradicted or not claimed. Pass accept_proof (e.g. "sample=attested; price<=listing") to learn whether the offer meets a buyer's requirements.

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": {
      "url": "<url>"
    },
    "name": "check_fair_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https URL of the paid endpoint
accept_proofNoOptional Accept-Proof value

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint) and the description correctly does not restate them. It instead adds genuinely new behavior: the call is free, it operates from outside the endpoint without payment, and it returns one of four verdicts per rule (verified, declared, contradicted, not claimed). That return-shape disclosure is valuable given there is no output schema; only edge behavior (e.g. non-x402 URLs, failures) is missing.

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?

Three tight sentences, front-loaded with the 'Free:' differentiator and the scope, then the return semantics, then the optional parameter use case. There is no filler, though the dense domain jargon ('Fair Offer rules', 'accept_proof') assumes familiarity and slightly slows parsing.

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?

For a two-parameter, read-only check with no output schema, the description supplies the essentials: cost, vantage point, and the shape of the result. The main gap is the unstated relationship to sibling tools such as check_offer, but nothing needed to invoke it correctly is absent.

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 would be 3, but the description goes beyond the schema by giving a concrete accept_proof example ('sample=attested; price<=listing'), which the schema only labels as 'Optional Accept-Proof value.' That example is the main thing an agent needs to construct the parameter correctly, so this earns 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?

The description uses a specific verb and resource ('check any x402 offer's Fair Offer block') and adds a distinguishing scope qualifier: it works 'from outside, without paying.' It does not explicitly differentiate itself from the near-named sibling check_offer, so an agent must infer the difference, but the free/external framing is concrete enough to identify the tool.

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?

Usage is implied rather than stated: 'Free: check ... without paying' suggests this is the no-cost path, and the accept_proof sentence describes a secondary use case (evaluating against buyer requirements). There is no explicit when-not guidance and no named alternative such as check_offer or conformance_check, leaving the agent to guess which sibling to pick.

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.