nds-mcp

Overview Schema Source Related Servers Discussions Admin

nds_query_gammas

Retrieve gamma-ray transitions for a nuclide from ENSDF, including energies, intensities, multipolarities, and conversion coefficients. Filter by level or gamma energy range.

Instructions

Query gamma-ray transitions from ENSDF. Returns energies, intensities, multipolarities, conversion coefficients for a nuclide.

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>",
      "limit": "<limit>"
    },
    "name": "nds_query_gammas"
  }
}

Input Schema

Name	Required	Description
`A`	Yes	Mass number
`Z`	Yes	Atomic number
`limit`	Yes
`level_energy`	No	Filter gammas from specific level (keV)
`gamma_energy_max`	No	Maximum gamma energy (keV)
`gamma_energy_min`	No	Minimum gamma energy (keV)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 9, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden for behavioral transparency. It states the return fields, which adds value, but does not disclose filtering capabilities, output structure, pagination, or any limits/caveats. The behavior is partially transparent but leaves key usage details unmentioned.

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 one sentence, front-loaded with the primary action and target. It includes essential return information without any filler. Every word contributes to understanding the tool's purpose.

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?

The description covers the core purpose and return types, which is sufficient given the high schema coverage. However, there is no output schema and the description does not mention the limit parameter or filter options, leaving minor gaps for a complete picture.

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 description coverage is high (83%), so the schema already explains most parameters (Z, A, energy filters). The description adds no parameter-specific meaning beyond 'for a nuclide', which maps to Z/A. Since the schema handles the heavy lifting, baseline 3 is appropriate.

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') and resource ('gamma-ray transitions from ENSDF'), and explicitly lists the returned data types (energies, intensities, multipolarities, conversion coefficients). This clearly distinguishes it from sibling tools like nds_query_levels and nds_query_decay_feedings, which target different nuclear data.

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 provides clear context: it is used for querying gamma-ray transitions from ENSDF for a nuclide, implying the need for Z and A. It does not explicitly name alternatives or exclusions, but the scope is well-defined by the query target.

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