Skip to main content
Glama
nii-research-mcp

nii-research-mcp

by koizumikento

search_researchers

Read-onlyIdempotent

Search KAKEN researchers by name, optionally filter by institution, to find research profiles and affiliations.

Instructions

Search KAKEN researchers by name and optionally by institution.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
limitNo
startNo
affiliationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the description only needs to add context. It adds none: no note on pagination despite limit/start parameters, no hint about result-set size, ordering, or that this queries an external Japanese research database whose coverage may be incomplete.

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, and the required identifier (name) comes first. It is not verbose, but the brevity reflects under-specification rather than tight editing of substantive content.

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 explained, but for a paginated open-world search tool with 0% parameter documentation the description leaves the agent guessing how to page and what happens past the result cap. Two of four parameters are effectively undocumented anywhere.

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 four parameters, so the description must compensate. It covers only name and affiliation (and only says the latter is optional), leaving limit and start — the pagination controls, with a max of 20 per page — entirely unexplained.

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?

States a specific verb and resource ("Search KAKEN researchers") plus the two filter axes (name, institution). The resource noun "researchers" distinguishes it from siblings like search_articles and search_projects without needing to name them, though no explicit sibling contrast is offered.

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?

There is no when-to-use / when-not-to-use guidance and no mention of alternatives such as search_records for narrower lookups. The word "optionally" hints that affiliation is a secondary filter, but that is a parameter cue, not usage routing.

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