StatOrigin

Search statistics

search

Read-onlyIdempotent

Search published StatOrigin statistics by indicator, place, industry, or words from the source sentence. Takes one query string (2–120 characters) and returns at most 20 results, each with id, title, and url. The url is the canonical record at https://statorigin.org/stat/{id}. Call fetch with id to read the value, unit, period, region, publisher, and source quote. Read-only: it does not change any record.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	What to search for. A year in the query filters the period.

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description still adds real behavioral facts beyond that: a hard cap of 20 results, the exact shape of each result (id, title, url), and the canonical URL pattern. It does not mention pagination or empty-result behavior, which keeps it from a 5.

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

Conciseness5/5

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

Purpose is front-loaded in the first clause, followed by constraints, result shape, canonical URL, and the follow-up call. Four sentences, each carrying distinct information, with no filler.

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

Completeness5/5

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

For a single-parameter search with an output schema present, the description covers everything the agent needs: what is searchable, the result cap, the result shape, the canonical identifier, and which tool to call next. Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single parameter is fully documented in the schema, including the 2-120 length bounds and the year-filters-period behavior. The description merely restates the character range, adding no syntax or formatting detail beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb and resource ('Search published StatOrigin statistics') and enumerates the searchable facets (indicator, place, industry, source-sentence words). It also positions itself against the sibling fetch by explaining that search returns ids which fetch then resolves, so an agent can distinguish the two without inspecting schemas.

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

Usage Guidelines4/5

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

Gives clear usage context and an explicit next step ('Call fetch with id to read the value...'), which is genuine routing guidance. It does not, however, say anything about when to prefer get_ranking over this tool, leaving one sibling unaddressed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All StatOrigin tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?