nii-research-mcp

search_projects

Read-onlyIdempotent

Search KAKEN research projects by keyword and paginate results with next_start to browse additional pages.

Instructions

Search KAKEN research projects by keyword. Use next_start to read the next page.

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

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

C2.6/5.0

Behavior2/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 without the description. The description's only added behavioral content is pagination — and it names "next_start", a field that does not exist in the schema, which is slightly misleading rather than clarifying. It says nothing about result size, matching behavior, or ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the purpose front-loaded, which is efficient. However, the second sentence spends its only words on a pagination field name that does not match the schema, so the brevity comes at the cost of correctness.

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?

An output schema exists, so return values need not be described. But for a three-parameter search tool with 0% schema coverage, the definition leaves the pagination model ambiguous (mismatched field name) and gives no hint about query syntax or result volume — a real gap for an agent trying 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% across three parameters, so the description must compensate and does not. It never explains what 'start' means (offset vs page number, default 1, max 200000) or what 'limit' controls (default 10, max 20), and its one parameter reference uses the wrong name (next_start instead of start).

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?

"Search KAKEN research projects by keyword" states a specific verb (search) and a specific resource (KAKEN research projects), plus the matching mode (keyword). It does not differentiate itself from siblings like search_articles or search_researchers, so it stops short of a 5.

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 only usage guidance is a pagination hint ("Use next_start to read the next page"). There is no statement of when to use this versus search_articles/search_records/search_researchers, and no mention of when to switch to get_project for a single project.

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

Deploy Server