Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

hms_get_origins

List the three HMS x402 data origins behind this MCP server (RE Data Refinery + HMS Storefront Data + HMS Trending Products), their openapi.json URLs, and how x402 payment works (402 + X-PAYMENT retry, USDC on Base). Free. Origin: null. 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": "hms_get_origins"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses that the call is free, that no inputs are needed, and that downstream access uses a 402 + X-PAYMENT retry with USDC on Base. It stops short of stating the access model plainly (e.g. read-only, no auth required, side-effect free), so the safety profile is inferred rather than declared.

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?

The core sentence is dense but earns its place by front-loading the resource and enumerating contents. The trailing fragment "Free. Origin: null. Price: free." is redundant boilerplate that repeats "free" twice and includes a null field carrying no information, which dilutes an otherwise tight description.

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

Completeness4/5

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

There is no output schema, so the description substitutes for one by naming the three origins and the fields returned (URLs plus payment mechanics). For a zero-parameter discovery tool that is sufficient to call it correctly, though the exact response shape or ordering is not stated.

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 applies. The description correctly implies a parameterless call by describing a fixed, enumerable result set.

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

Purpose5/5

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

The description opens with a specific verb and resource ("List the three HMS x402 data origins behind this MCP server") and enumerates exactly what each entry contains: the three named origins, their openapi.json URLs, and the x402 payment flow. This is clearly a discovery/meta tool, distinct from every sibling, which are data-query endpoints.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the word "List" and the mention of payment mechanics, which suggests calling it to discover origins and understand how to pay. There is no explicit when-to-use statement, no guidance on when it should precede the sibling data tools, and no named alternative for any overlapping need.

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.