Skip to main content
Glama

x402 Price Index / Fair Price Check

market_price_index
Read-onlyIdempotent

x402 Price Index / Fair Price Check: the going rate for a capability across listed x402 endpoints: comparables, sellers, min / p25 / median / p75 / max and usage-weighted median; pass price_usd (or a listed url) to get its percentile and FAIR / LOW / ABOVE_MARKET / HIGH. By OMENZ. (MCP calls run in AYNE, the free playzone; production: GET https://www.omenz.org/api/tollbooth/v1/market/price-index, $0.002 via x402.)

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": {
      "q": "<q>"
    },
    "name": "market_price_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYessearch text
urlNofull https URL to check
price_usdNoprice usd
min_payersNomin payers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / min_payers / description
      Added value: +"min payers"
    • addedInput schema / properties / price_usd / description
      Added value: +"price usd"
    • addedInput schema / properties / q / description
      Added value: +"search text"
    • addedInput schema / properties / url / description
      Added value: +"full https URL to check"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the production endpoint, the $0.002 x402 cost, and the note that MCP calls execute in the free AYNE playzone — all material to an agent deciding whether to call it. It stops short of describing pagination or how many endpoints the index covers.

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?

The core purpose, the returned statistics, and the input-to-output mapping are front-loaded in the first two clauses, so an agent gets the essentials immediately. The trailing 'By OMENZ' and the deployment/cost parenthetical are secondary but still informative rather than 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 four parameters and no output schema, the description carries the burden of describing returns, and it does so by naming the full stat set and the four classification labels. What remains thin is the relationship between the optional filters (q, min_payers) and those results, but an agent has enough to call it correctly.

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 q, url, price_usd and min_payers, making 3 the baseline. The description adds the meaningful distinction that url should be 'a listed' URL from the index and that price_usd drives the percentile output, but it says nothing about q or min_payers and their interaction with the returned distribution.

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 the resource precisely (going rate for a capability across listed x402 endpoints) and enumerates the statistics it returns plus the FAIR/LOW/ABOVE_MARKET/HIGH classification. It is clearly a pricing-benchmark query rather than a seller lookup or a payment action, which separates it from siblings like market_sellers or market_payee, though it never names an alternative explicitly.

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 through 'pass price_usd (or a listed url) to get its percentile', which tells the agent what input triggers a fair-price check. There is no explicit when-to-use/when-not guidance, no statement of prerequisites, and no routing to sibling tools such as market_find or cost_estimate for adjacent questions.

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.

Resources