jp-statistics-mcp

search_indicators

Read-onlyIdempotent

Find Japanese statistical indicator codes by searching indicator names in Japanese or English. Use it to locate the exact code needed to query dashboard data.

Instructions

Find indicator codes by Japanese or English text in the indicator name.

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": {
      "query": "<query>"
    },
    "name": "search_indicators"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`offset`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that matching is textual and bilingual, but says nothing about substring vs prefix matching, result ordering, or that results are paginated despite limit/offset parameters.

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?

A single front-loaded sentence with zero filler; the searched field and the language support are stated up front. It is slightly under-specified rather than verbose, which is the better failure mode for so short a description.

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?

For a simple three-parameter search tool with an output schema (so return values need no explanation), the description covers the core intent and is roughly adequate. It nonetheless leaves the pagination parameters and the nature of the text match unexplained, which an agent needs to page through results correctly.

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%, so the description carries the full burden, yet it only clarifies the 'query' parameter indirectly ('by Japanese or English text in the indicator name'). The 'limit' and 'offset' parameters are documented nowhere, and no format or matching-syntax details are added beyond the schema's pattern and maxLength constraints.

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 ('Find'), a specific resource ('indicator codes'), and the exact field searched ('indicator name'), plus the useful detail that matching works on Japanese or English text. That is enough to distinguish it from get_indicator_data, which retrieves data rather than resolving names to codes, though the sibling is never named.

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 usage is only implied: an agent can infer this is a lookup step preceding get_indicator_data, but the description never states when to use it, when not to, or what to do with the returned codes. No prerequisites or guidance about searching only when a code is unknown are given.

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

Deploy Server