Skip to main content
Glama
nii-research-mcp

nii-research-mcp

by koizumikento

search_records

Read-onlyIdempotent

Query CiNii Research to find articles, books, projects, researchers, and other records; restrict results to a specific record kind when needed.

Instructions

Search CiNii Research across all records or restrict to the specified record kind.

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

Input Schema

NameRequiredDescriptionDefault
kindNoall
limitNo
queryYes
startNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered without the description. The description adds nothing behavioral beyond that: no mention of pagination behavior, per-request result caps, result ordering, or coverage of the external index. For a search tool over an open-world catalog, that is a thin contribution.

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 or redundancy. It is efficient, though brevity here is partly under-specification rather than disciplined concision.

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 shape need not be explained, and annotations cover safety. Still, for a 4-parameter search tool with zero schema description coverage, the definition omits query syntax, pagination semantics, result caps, and how `kind` maps to the typed sibling tools — gaps an agent would need to call it 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%, so the description must carry the meaning of all four parameters. It only references `kind` indirectly ("specified record kind") and says nothing about `query` syntax or matching semantics, `limit` (max 50), or `start` (pagination offset, max 10000). The enum values exist in the schema but the description does not clarify their meaning or default behavior.

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 CiNii Research") plus the scoping option ("all records or restrict to the specified record kind"). It does not name the sibling type-specific tools (search_articles, search_projects, search_researchers), so the agent must infer that this is the general-purpose entry point, but the core action is unambiguous.

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?

"Across all records or restrict to the specified record kind" implies a broad-vs-narrow choice, which hints that this tool can subsume the typed siblings. However, there is no explicit when-to-use/when-not guidance and no statement of the alternative specialized search tools, leaving routing to the agent's inference.

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