jp-statistics-mcp

search_surveys

Read-onlyIdempotent

Find Japanese statistical surveys by name or code, returning agency, summary, and reference link.

Instructions

Find statistical surveys by name or code, with agency, summary and reference link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_surveys"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds that hits carry agency, summary and a reference link, which is useful shape information, but an output schema exists and pagination/result-cap behavior is left unmentioned. Modest added value beyond structured fields.

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?

A single front-loaded sentence with no filler: the search targets and the returned fields are stated immediately. Nothing could be removed without losing information.

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?

For a simple three-parameter search with an output schema and full annotation coverage, the description supplies enough to call it correctly: what is searched and what comes back. The remaining gap is paging behavior and result-set expectations, which is a minor omission rather than a blocker.

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 0%, so the description must carry parameter meaning; 'by name or code' does explain the semantics of 'query' (free-text over names and codes). However the two paging parameters, limit (default 10, max 100) and offset (max 10000), get no explanation of default page size or how to page through large result sets.

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?

Names a specific verb ('Find') and resource ('statistical surveys') and specifies the matching keys (name or code), which separates it from siblings like search_indicators and search_series by resource type. It stops short of explicitly contrasting with those siblings, but the resource noun does the disambiguating work.

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?

Usage is only implied: an agent can infer this is the entry point when it has a survey name or code and none of the get_* data tools apply. There is no explicit when-to-use/when-not statement, no mention of paging through results, and no guidance on combining it with the series/indicator tools.

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

Deploy Server