Skip to main content
Glama

Estat Japan Get Metadata

estat_japan_get_metadata
Read-onlyIdempotent

Fetch the dimension definitions and code lists for a specific e-Stat statistics table (statsDataId). Returns category codes needed to construct filters for get_data. Requires _apiKey.

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": {
      "stats_data_id": "0000150001"
    },
    "name": "estat_japan_get_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoJ | E
stats_data_idYesTable ID (statsDataId)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 open-world behavior, so the bar is lower. The description adds meaningful context beyond them: the tool reads metadata for a specific table, returns category codes, and requires _apiKey authentication — an operational prerequisite the annotations do not convey.

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?

Three short sentences, front-loaded with the core purpose and followed by the return value and auth requirement. Every sentence carries distinct information with no filler or repetition.

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

Completeness4/5

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

With annotations covering the safety profile and an output schema documenting return values, the description supplies what is left: purpose, the relationship to get_data, and the _apiKey requirement. It is essentially complete for this complexity, though it stops short of mentioning result size, pagination, or the lang parameter's effect.

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 both parameters are already documented in the schema. The description reinforces the meaning of statsDataId as the table identifier but adds no syntax, format, or guidance for the optional lang parameter, so it sits at the baseline rather than exceeding it.

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 uses a specific verb ('Fetch') plus a precise resource ('dimension definitions and code lists') and ties it to a named identifier (statsDataId). It also distinguishes the tool's role from the sibling get_data by framing its output as the codes needed to build filters for that tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly positions the tool as a precursor to get_data ('Returns category codes needed to construct filters for get_data'), which effectively communicates when to call it. What is missing is any explicit when-not-to-use guidance or statement about whether this is required versus optional before fetching data.

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.