Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

sf_v1_coverage

Free — real record counts per dataset (honesty gate) Origin: https://storefront-data-hms.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": "sf_v1_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it only supplies pricing/marketing metadata ('Free', 'Price: free') and an origin URL. It does not describe the response shape, whether the counts are live or cached, or any failure modes of the 'honesty gate'.

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?

It is short, but 'Free' at the front and 'Price: free' at the end duplicate the same information, and the origin URL is operational noise for an agent deciding whether to call it. The useful clause, 'real record counts per dataset', is buried mid-sentence.

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?

With no parameters and no output schema, the description must explain what comes back, and it only partially does so ('record counts per dataset'). It does not say which datasets are covered or how the counts are structured.

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, so there is no schema semantics to add to; baseline 4 applies. The phrase 'per dataset' hints at output grouping rather than an input, which is a minor inconsistency but not harmful.

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?

It states the resource (record counts per dataset) but omits a verb and leans on opaque jargon ('honesty gate'). Nothing distinguishes it from the sibling 'refinery_v1_coverage', so an agent must guess which coverage tool matches its target dataset.

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 prerequisites, and no mention of when another coverage or health tool is the better choice. The agent is left to infer invocation context from the name alone.

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.