jp-statistics-mcp

get_series_data_by_layer

Read-onlyIdempotent

Fetch Japanese statistical time-series observations by comma-separated layer path (e.g., '1,2,*') and resume results from a start position for paginated retrieval.

Instructions

Fetch observations by comma-separated layer path (e.g. '1,2,*'). Resume from NEXTPOSITION.

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": {
      "database": "<database>",
      "frequency": "<frequency>",
      "layer": "<layer>",
      "start_period": "<start_period>",
      "end_period": "<end_period>"
    },
    "name": "get_series_data_by_layer"
  }
}

Input Schema

Name	Required	Description	Default
`layer`	Yes
`database`	Yes
`frequency`	Yes
`end_period`	Yes
`start_period`	Yes
`start_position`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so safety and repeatability are covered without description help. The description does add genuinely new behavior: results are paginated and resumable via a NEXTPOSITION token. However, it never explains what NEXTPOSITION is, how it relates to the start_position parameter, or what happens when the token is exhausted, leaving the resume mechanic underspecified.

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?

Two short sentences with the layer-path constraint and its example front-loaded, and no filler wording. The terseness comes at the cost of under-specification rather than verbosity, but structurally it is efficient.

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, but the tool still has six parameters with five required and no schema descriptions, and the description leaves most of them opaque. The undefined NEXTPOSITION token and the unstated relationship to start_position make the pagination contract ambiguous for a complex, multi-parameter retrieval call.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, so the description must carry the burden, and it only addresses layer (comma-separated path with a wildcard example) and alludes vaguely to resuming via NEXTPOSITION. The database, frequency, start_period, and end_period parameters get no meaning beyond their regex patterns, and the resume hint does not even use the actual parameter name start_position.

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 gives a specific verb ('Fetch') and resource ('observations') plus the distinguishing dimension ('by layer path'), so an agent can tell it is layer-scoped retrieval rather than the plain series or indicator tools. It stops short of naming how it differs from get_series_data or get_multiple_series_data, so sibling differentiation is only implied by the layer path.

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 statement of when to choose this over get_series_data, get_multiple_series_data, or get_indicator_data, and no prerequisites or exclusions are given. The only usage-adjacent hint is the pagination remark about resuming from NEXTPOSITION, which does not tell an agent when this tool is the right entry point.

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

Deploy Server