Skip to main content
Glama
Sign In
nds-mcp

nds-mcp

by fkguo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

nds_get_exfor_entry

Retrieve a complete EXFOR entry with all subentries and data points by specifying the entry number.

Instructions

Get one EXFOR entry (all subentries + points) by entry number.

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

Input Schema

NameRequiredDescriptionDefault
entry_idYesEXFOR entry number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose that the result includes all subentries and points, which is useful, but it does not mention output format, potential large payload, error behavior, or whether any specific access conditions apply.

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 communicates the essential purpose and scope with no redundant 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?

Given the simplicity of a one-parameter retrieval tool and no output schema, the description adequately covers what the tool returns. Minor gaps remain around error handling and output size, but the core information is present.

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 schema fully describes the only parameter (entry_id as 'EXFOR entry number'), and the description adds no extra semantics beyond restating that the tool works by entry number. This meets the baseline for high schema coverage.

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 states the tool retrieves one EXFOR entry including both subentries and data points, keyed by entry number. This specific verb-plus-resource pairing differentiates it from sibling search and listing tools.

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 implies usage: use when you have a known EXFOR entry number and need the full entry. It does not explicitly name alternatives or when-not-to-use, but the context is clear enough for a simple lookup tool.

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

Deploy Server

Other Tools