Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

sf_v1_rental_rates

Fetch verified daily car-rental rates per class — $0.03 per call Origin: https://storefront-data-hms.ares-hms.workers.dev. Price: $0.03 per call via x402 (USDC on Base).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sf_v1_rental_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity with verified rate coverage, e.g. Columbus (Columbus, OH pilot)
x402_paymentNoOptional. X-PAYMENT header value an x402 client produced after settling this exact origin+params challenge. Omit to first receive the Payment Required challenge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior beyond the name: a metered cost ($0.03/call), a payment rail (x402, USDC on Base), and a specific origin. However, it says nothing about what the response contains, whether rates are per-day per-class, coverage limits, or failure modes when a city lacks coverage.

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

Conciseness3/5

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

The description is short and front-loads the purpose, which is good. But the price '$0.03 per call' is stated twice in two sentences, and a bare origin URL is inlined into the prose rather than being actionable context — a meaningful fraction of this very short text is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the definition must explain return values; it does not say what a 'rate per class' record looks like. It compensates partially by explaining payment mechanics, but an agent still cannot predict the response shape.

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%, including a concrete example for `city` and a full explanation of the x402 challenge flow, so the baseline is 3. The description adds only the phrase 'per class' and 'daily', which hint at result granularity but do not clarify parameter meaning beyond the schema.

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: 'Fetch verified daily car-rental rates per class'. The domain ('car-rental rates') and freshness ('daily') are clear enough to distinguish it from the fuel-price, sleep-stop and refinery siblings without opening a schema, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no prerequisites, and no alternative tool for related queries. The only usage-adjacent information — omitting x402_payment to receive the 402 challenge — lives in the schema, not the description.

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.