Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

refinery_health

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 discloses only that the call costs nothing and which origin it hits. It says nothing about auth requirements, rate limits, whether the read is safe, or what the returned health/cache payload looks like — all of which matter for a tool with zero structured disclosure.

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 structure is a run-on fragment where the origin URL is glued onto the purpose sentence with no punctuation, and cost is stated twice ('Free —' and 'Price: free'). The core purpose is front-loaded, but the redundancy and awkward phrasing cost readability.

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 output schema and no annotations, the description should at minimum describe the shape of the health/cache response and note that no credentials are needed. It covers the what and the origin but leaves the return value and access requirements unexplained, which is only partially adequate for a zero-parameter monitoring endpoint.

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 input schema defines zero parameters with additionalProperties false, so there is nothing for the description to clarify; baseline 4 applies. The description correctly implies a no-argument call.

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

Purpose4/5

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

The description names the resource and what is returned: 'service health and cache size' for the Origin at re-data-refinery.ares-hms.workers.dev. That is enough to pick this over the data-fetching siblings (refinery_properties, refinery_auctions, etc.), though it never explicitly distinguishes itself from sf_health, the apparent sibling health check.

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 explicit when-to-use or when-not-to-use guidance, no mention of prerequisites, and no comparison to sf_health or hms_get_origins. The only usage-adjacent signal is 'Free', which speaks to pricing rather than to selection.

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.