Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

sf_v1_truck_fuel_prices

Fetch weekly US average diesel prices (24 points) — $0.02 per call Origin: https://storefront-data-hms.ares-hms.workers.dev. Price: $0.02 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_truck_fuel_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
weeksNoNumber of trailing weekly points to return (default 24, max 24)
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

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavioral context: it discloses per-call cost, the origin, and the x402 payment rail (USDC on Base). It still omits failure modes, rate limits, or whether results are cached, but the commercial terms are unusually well surfaced.

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 sentence is short but sloppily assembled: the price '$0.02 per call' is stated twice, and an em-dash splices origin/cost metadata into a run-on. Nothing is wasted in content, but the duplication and lack of front-loading structure cost it.

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?

For a paid, annotation-free tool with no output schema, the description covers cost and payment mechanics but says nothing about the response shape (what a weekly point contains) or behavior when the payment header is invalid. Adequate, but not complete enough for a pay-per-call endpoint.

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 coverage is 100%, so both parameters (weeks, x402_payment) are already documented in the schema. The description adds no new parameter-level meaning beyond restating the price/payment context, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Fetch weekly US average diesel prices') plus the granularity ('24 points'), which is enough to tell it apart from siblings like sf_v1_truck_sleep_stops or sf_v1_rental_rates without opening a schema.

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?

There is no guidance on when to call this versus alternatives, nor any preconditions beyond the price note. A reader must infer the use case (trucking/fuel cost modeling) entirely from the resource name.

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.