nds-mcp

Overview Schema Source Related Servers Discussions Admin

nds_query_decay_feedings

Retrieve beta and electron capture decay feeding patterns from ENSDF, returning branching ratios, log(ft) values, and endpoint energies for a specified parent nuclide and optional decay mode.

Instructions

Query beta/EC decay feeding patterns from ENSDF. Returns branching ratios, log(ft) values, endpoint energies for parent nuclide decays.

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": {
      "Z": "<Z>",
      "A": "<A>"
    },
    "name": "nds_query_decay_feedings"
  }
}

Input Schema

Name	Required	Description
`A`	Yes	Parent mass number
`Z`	Yes	Parent atomic number
`decay_mode`	No	Filter by decay mode

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 9, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It reveals the return contents but does not disclose whether the operation is read-only, requires authentication, has rate limits, or behaves differently for invalid nuclides. The query nature is implied but not explicitly stated as safe.

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?

A single, front-loaded sentence that states the purpose and expected outputs. Every word contributes, with no redundancy or filler.

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 simple query tool with three parameters and no output schema, the description adequately names the returned data types. It is slightly incomplete on usage scenarios and safety, but the core behavior is well covered.

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 100%, with each parameter described in the schema. The description adds context by framing Z/A as 'parent nuclide' and linking to decay modes, but it does not provide new syntax or format details beyond the schema.

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 uses a specific verb 'Query' with a clear resource ('beta/EC decay feeding patterns from ENSDF') and lists concrete returned data (branching ratios, log(ft), endpoint energies). This distinguishes it from siblings like nds_get_decay or nds_query_levels.

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?

No guidance is given on when to use this tool versus alternatives such as nds_get_decay or nds_query_gammas. The description states what it does but does not mention exclusions, prerequisites, or preferred contexts.

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