nds-mcp

by fkguo

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

nds_lookup_reference

Retrieve bibliographic references from ENSDF/NSR nuclear databases by keynumber or mass number.

Instructions

Look up ENSDF/NSR bibliographic references by keynumber or mass number.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nds_lookup_reference"
  }
}

Input Schema

Name	Required	Description	Default
`A`	No	Mass number (list all references for this A)
`keynumber`	No	NSR keynumber (e.g. "2012WA38")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 9, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action without mentioning return format, data source details, or any side effects. For a type of operation, it provides almost no behavioral transparency beyond the tool name.

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 that directly states the tool's purpose without excessive wording.

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

Completeness3/5

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

The description is adequate for a simple tool with two optional parameters, but it does not describe the return format or behavior when no references are found. Given the absence of an output schema and annotations, a bit more detail would improve completeness.

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?

The input schema fully documents A and keynumber with descriptions. The description adds the 'or' relationship indicating that either parameter can be used, which is helpful but not extensive. Since schema coverage is 100%, the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool's function as looking up bibliographic references, specifies the two lookup keys (keynumber and mass number), and differentiates it from sibling tools like nds_query or nds_search which handle broader data queries.

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

Usage Guidelines4/5

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

The description gives clear context for when to use this tool: to retrieve references by NSR keynumber or mass number. However, it does not explicitly name alternative tools or state when not to use it, so it falls short of the highest bar.

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