e-stat-dashboard-mcp

get_indicator_data

Read-onlyIdempotent

Retrieve statistical series data by indicator code and filter by region or cycle to get specific e-Stat Dashboard values; use limit and offset to page results.

Instructions

Get series data. Cycles: 1 month, 2 quarter, 3 calendar year, 4 fiscal year.

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": {
      "indicator_code": "<indicator_code>"
    },
    "name": "get_indicator_data"
  }
}

Input Schema

Name	Required	Default
`cycle`	No
`limit`	No
`offset`	No
`region_code`	No	00000
`indicator_code`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

C2.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond a cycle legend: it does not mention pagination behavior for the limit/offset parameters, rate limits, or the shape of the returned series. With rich annotations the lower burden is met, but the added behavioral context is minimal.

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 description is brief and front-loads the verb, but the second sentence is cryptic and lacks context (e.g. what a "cycle" controls). It is concise without being informative.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. However, for a five-parameter tool with 0% schema description coverage, the description is missing critical parameter details and sibling differentiation, leaving an agent without enough information to call it correctly.

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

Parameters1/5

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

Schema description coverage is 0% across five parameters, so the description must carry the burden. It only explains the cycle values (and ambiguously, e.g. "2 quarter"), while leaving indicator_code's 19-digit pattern, region_code's 5-digit pattern, limit and offset completely undocumented. This does not compensate for the schema gap.

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?

"Get series data" states a verb and generic resource but does not identify that it returns indicator series, nor distinguish it from the sibling search_indicators tool. An agent must infer the purpose from the tool name rather than the description.

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?

The description gives no when-to-use or when-not-to-use guidance, and does not mention search_indicators as an alternative for discovery. Only the cycle codes are explained, which is parameter semantics rather than usage guidance.

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

Deploy Server