StatOrigin

Get a country ranking

get_ranking

Read-onlyIdempotent

Read one published country ranking by the slug of its https://statorigin.org/rankings/{slug} page. Example: crude-steel-production-by-country. Returns the comparable period and at most 20 rows. Each row has rank, value, unit, region, publisher, statistic id, and canonical url. If scan_capped is true, open the ranking URL for the complete table. Read-only: it does not invent a ranking the site does not publish.

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": {
      "slug": "<slug>"
    },
    "name": "get_ranking"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Path segment after /rankings/.

Output Schema

Name	Required	Description	Default
`url`	Yes
`rows`	Yes
`slug`	Yes
`unit`	Yes
`title`	Yes
`period`	Yes
`row_count`	Yes
`truncated`	Yes
`scan_capped`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavior beyond that: a 20-row result cap, the scan_capped flag and its follow-up, and the guarantee that it will not fabricate an unpublished ranking. The 'Read-only' clause is mildly redundant with readOnlyHint but not contradictory.

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

Conciseness4/5

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

Four sentences, each carrying distinct information, with the core purpose front-loaded before return shape, follow-up behavior, and safety. Only the trailing 'does not invent a ranking the site does not publish' phrasing is slightly muddy and could be tighter.

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 read tool with a full output schema, the description covers everything an agent needs: the identifier format, the row cap, the partial-result escape hatch, and the safety posture. Nothing required for a correct call is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by giving the full URL pattern and a concrete example slug ('crude-steel-production-by-country'), clarifying the expected format beyond the schema's terse 'Path segment after /rankings/.'

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 ('Read one published country ranking') and pins down the exact access path via the /rankings/{slug} URL template, which is far more specific than the generic siblings fetch and search. An agent can tell immediately that this is the targeted ranking reader rather than a general fetch or search.

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 implied by the slug-based lookup, and there is one conditional next step ('If scan_capped is true, open the ranking URL for the complete table'). However, there is no explicit guidance on when to choose this tool over fetch or search, which is the selection decision an agent actually faces.

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?