jp-statistics-mcp

search_series

Read-onlyIdempotent

Find Bank of Japan time-series by Japanese name, English name, or series code in a specified database, with pagination and configurable result limits.

Instructions

Find series by Japanese name, English name or code within a BOJ database.

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

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, open-world operation. The description adds scope by identifying the searchable fields and BOJ database context, but it does not disclose matching semantics such as exact versus substring search, case sensitivity, or pagination behavior.

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?

The description is a single front-loaded sentence with no filler or redundant wording. Every phrase contributes to identifying the resource and search fields.

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

Completeness2/5

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

Although an output schema and annotations reduce the burden, the tool still has four parameters with no schema descriptions. The description leaves important search behavior and the database and pagination parameters unexplained, so an agent lacks enough context to call it confidently without additional inference.

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 must compensate for all four parameters. It partially clarifies that query may contain a Japanese name, English name, or code and that the search occurs within a BOJ database, but it says nothing about the database parameter's valid values or the meaning of limit and offset.

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 states a specific verb and resource: finding series by Japanese name, English name, or code within a BOJ database. It is clear what the tool searches, but it does not explicitly distinguish itself from sibling retrieval tools such as get_series_data or the other search_* tools.

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

Usage Guidelines2/5

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

The description implies that the tool is used to look up series by name or code, but gives no explicit guidance on when to use it instead of get_series_data or other search tools. It also omits prerequisites, pagination expectations, or any when-not-to-use conditions.

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

Deploy Server