Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_v1_coverage

Free — alias of /coverage Origin: https://re-data-refinery.ares-hms.workers.dev. Price: free.

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": "refinery_v1_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses only pricing (free) and an origin URL; it says nothing about what the call returns, whether it is a read-only lookup, side effects, rate limits, or response shape — leaving an agent unable to predict behavior.

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?

Very short, which is appropriate, but the content is redundant — "Free" is stated twice (as label and "Price: free") and the origin URL is fronted ahead of any functional information. It reads like scraped API metadata rather than a purpose statement.

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

Completeness2/5

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

For a zero-parameter, no-output-schema tool, the description must at minimum convey what data comes back. It instead gives pricing and an origin host, so an agent still cannot tell what invoking it will produce or whether it is safe to call.

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?

The tool takes zero parameters (empty object, additionalProperties false), so there is no parameter semantics to explain; the baseline of 4 applies. The description neither helps nor harms here.

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

Purpose2/5

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

"Alias of /coverage" essentially restates the tool name (refinery_v1_coverage) without explaining what "coverage" refers to — API coverage, data coverage, endpoint availability? The alias disclosure is mildly useful given siblings like refinery_coverage exist, but it does not state whether the two are identical or how they differ.

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?

No when-to-use guidance at all. "Free" and "Price: free" hint that cost is not a concern when calling it, but there is no indication of what an agent would call this for, or when to prefer it over refinery_coverage.

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.