jp-statistics-mcp

search_terms

Read-onlyIdempotent

Find Japanese statistical terms by name or code to read definitions and reference links.

Instructions

Find statistical terms by name or code and read definitions and reference links.

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_terms"
  }
}

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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that results include definitions and reference links, but it omits behavior the schema hints at — pagination via limit/offset and the fact that query is optional (default null), which likely means 'list all terms'.

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 no filler; the resource and the returned content come first. Brevity is appropriate, though one more clause on paging would have earned its place.

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

Completeness5/5

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

An output schema exists, so return values need not be described, and the annotations carry the safety profile. What remains missing — paging and empty-query behavior — is minor for a simple read-only search tool, though it slightly caps this dimension.

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% across all three parameters, so the description must compensate and largely does not. 'By name or code' gives meaning to query, but limit and offset (with their 1-100 and 0-10000 bounds and defaults) are never explained in the description.

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?

Uses a specific verb-plus-resource ('Find statistical terms') and adds what the caller gets back ('definitions and reference links'). It is clearly distinguishable from the indicator/series/region siblings by resource type, though it never explicitly contrasts itself with them.

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?

Implied usage only: 'by name or code' hints at how the query should be formed, but there is no statement of when to prefer this over search_indicators or the other search siblings, no prerequisites, and no note on what happens when no query is supplied.

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

Deploy Server