nii-research-mcp

get_record

Read-onlyIdempotent

Retrieve selected CiNii Research metadata for a CRID returned by search to inspect article or research record details.

Instructions

Get selected CiNii Research metadata for a CRID returned by search.

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

Input Schema

Name	Required	Description	Default
`crid`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds only that the returned metadata is 'selected' (partial) and that the input should originate from search; it says nothing about behavior for a nonexistent or malformed CRID.

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?

One sentence, front-loaded with the verb and resource, with the provenance constraint appended where it is useful. No redundant or filler wording.

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

Completeness4/5

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

For a single-parameter read tool with rich annotations and an output schema, the description covers purpose, input provenance, and partial-return nature. Nothing essential is missing, though error behavior on invalid CRIDs is unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single parameter, so the description must compensate; it does add provenance meaning (the CRID comes from search results), but not the format constraint captured only in the schema pattern (^[0-9]{1,20}$). Partial compensation for a low-coverage parameter.

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 ('Get') and resource ('CiNii Research metadata for a CRID'), and the phrase 'returned by search' positions it as the detail-fetch counterpart to the search_* siblings. It stops short of naming an alternative explicitly, and 'selected metadata' leaves the field set vague, so it is clear but not fully differentiated.

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?

The phrase 'for a CRID returned by search' implies the intended workflow (search first, then fetch details), which is genuine usage guidance. There is no explicit when-not guidance or handling instructions for a CRID obtained elsewhere.

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

Deploy Server