Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

sf_health

Free — service health and resource list 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_health"
  }
}

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 supplied, so the description carries the full behavioral burden, yet it only discloses that the call is free and gives an origin URL. It does not say what the health output contains, whether it is a liveness probe, what a failure looks like, or whether auth is involved (beyond the implied 'free'). For a zero-parameter operational endpoint this is thin.

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 the word 'free' appears twice ('Free —' and 'Price: free') and the origin URL is concatenated without punctuation separating it from the purpose, making the sentence harder to parse. The redundant pricing statement wastes space that could have described the response.

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?

With no annotations and no output schema, the description is the only source of behavioral information, and it omits what the health/resource response looks like and what the caller should do with it. The only substantive content is pricing metadata and an origin URL.

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 nothing for the description to disambiguate and the baseline of 4 applies. No parameter-related gaps exist.

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?

The phrase 'service health and resource list' does give a rough sense of the resource (a health/status endpoint that also lists resources), but it is a compound and vague statement without a clear verb, and it does nothing to separate this tool from the sibling 'refinery_health' which appears to serve the same role for another service. An agent cannot confidently predict what the tool returns from this wording.

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 about when to call this versus 'refinery_health' or any other sibling, no stated prerequisites, and no exclusions. The only usable signal is that it is free, which is not a usage condition.

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.