Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_coverage

Free — real record counts per dataset 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_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 pricing ('Free') and an origin URL, but says nothing about whether it returns a single object or a per-dataset mapping, whether results are cached, or any rate limits. Pricing is a behavioral trait, but not one that helps correct invocation.

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

Conciseness2/5

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

It is short but poorly structured: a fragment with an em dash, then a raw URL, then 'Price: free' which redundantly repeats the leading 'Free —'. Nothing is front-loaded with a verb.

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 zero-parameter tool with no output schema and no annotations, the description should explain the return shape and what a 'dataset' is; it hints at per-dataset counts but leaves the format unstated. The URL and pricing are present, but the essentials are not.

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?

Zero parameters means the schema baseline is 4, and there is nothing for the description to clarify. No parameter confusion is possible.

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

Purpose3/5

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

"Free — real record counts per dataset" names the resource (record counts per dataset) but uses no clear verb; the agent must infer it returns counts. It does not distinguish this from refinery_v1_coverage, which from the name appears to do something similar.

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 when-to-use guidance, no named alternative, and no exclusions. The only hints are 'Free' and an origin URL, which do not route the agent between this tool and refinery_v1_coverage or sf_v1_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.