Skip to main content
Glama
cygkichi
by cygkichi

get_specific_e_stat_data

Retrieve specific statistical data from the e-Stat API using a dataset ID or statistics table ID. Specify the data set or stats table ID to fetch numeric data with optional pagination.

Instructions

Retrieves specific statistics data from the E-Stat API.
機能名:統計データ取得
指定した統計表ID又はデータセットIDに対応する統計データ(数値データ)を取得します。

Args:
    data_set_id (str or None): The ID of the dataset(データセットID).
    stats_data_id (str or None): The ID of the statistics data(統計表ID).
    # Ensure that either data_set_id or stats_data_id is provided, but not both
    if not data_set_id and not stats_data_id:
        raise ValueError("Either 'data_set_id' or 'stats_data_id' must be provided.")
    if data_set_id and stats_data_id:
        raise ValueError("Only one of 'data_set_id' or 'stats_data_id' should be provided.")

    startPosition (int): The starting position for the search results.
        Defaults to 1. For example:
            - To get the first 100 results, set startPosition to 1.
            - To get the next 100 results, set startPosition to 101.
    limit (int): The maximum number of results to retrieve.
        Defaults to 100.

Returns:
    str: The response text from the E-Stat API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
data_set_idNo
startPositionNo
stats_data_idNo
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the validation rule (exactly one of the two IDs), pagination via startPosition and limit, and the return type as a string. This goes beyond the schema, though it does not discuss error handling or rate limits.

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 structured but includes redundant Japanese and English text and embeds Python validation code, which adds unnecessary length. The core information is clear but could be more concise.

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 description covers parameter usage and pagination well, but it provides minimal detail on the response format (only 'response text') and no error or edge-case behavior. Given no output schema or annotations, this leaves some gaps for the agent.

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

Parameters5/5

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

With 0% schema description coverage, the description fully explains all four parameters: the two ID types, startPosition with an example for pagination, and limit. It also adds the critical constraint that exactly one ID must be provided, which is not in the schema.

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?

The description clearly states the tool retrieves specific statistics data from the E-Stat API using a specific verb and resource. It distinguishes itself from sibling tools such as search_e_stat_tables and get_e_stat_meta_info by focusing on data retrieval by ID.

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?

The description implies usage by requiring either data_set_id or stats_data_id, but it does not explicitly compare to sibling tools or state when not to use it. No exclusions or alternatives are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cygkichi/estat-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server