Skip to main content
Glama

Estat Japan Get Data

estat_japan_get_data
Read-onlyIdempotent

Fetch observations from a stats table. Optionally filter by dimension codes.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 3,
      "stats_data_id": "0000150001"
    },
    "name": "estat_japan_get_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoJ | E
limitNo1-100000 (default 100)
filtersNoDimension code filters as { "cdCat01":"A03503", "cdTime":"2023" }
stats_data_idYesTable ID (statsDataId)
start_positionNo1-based row offset

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The description is consistent with the annotations, which already declare read-only, idempotent, non-destructive, and open-world behavior. Beyond that, it adds little behavioral context such as rate limits, pagination behavior, or data freshness, but the annotations and output schema carry much of that burden.

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?

The description is two short sentences with no wasted wording and the main purpose is front-loaded. It is appropriately sized for a tool whose schema and annotations carry the detailed structure.

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

Completeness3/5

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

The tool has five parameters, a nested filters object, and an output schema, so the description does not need to restate every field. However, given the e-Stat context, it is thin on how this tool relates to metadata discovery and what the returned observations represent.

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%, so the schema already documents all five parameters, including filters and pagination. The description mentions optional dimension-code filtering but adds no syntax or meaning beyond what the schema and examples already provide.

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 states a clear verb and resource: fetching observations from a stats table. It does not explicitly distinguish this from the sibling metadata tool, so it is clear but not fully differentiated.

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 only usage guidance is that dimension-code filtering is optional. There is no explicit guidance on when to use this tool instead of estat_japan_get_metadata or list_data_catalog, and no prerequisites or exclusions are mentioned.

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.