Skip to main content
Glama

get_subatomic_particle

Retrieve details for a single subatomic particle by ID, including its particle group and optional child quantum states or raw embedding for physics model queries.

Instructions

Retrieve details of a single subatomic particle including its particle group and child quantum states.

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": {
      "id": "<id>"
    },
    "name": "get_subatomic_particle"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSubatomic Particle ID
include_embeddingNoInclude raw 1024-float vector embedding
include_quantum_statesNoInclude child quantum states

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, but "Retrieve" does convey a non-mutating read. It adds the useful behavioral fact that child quantum states are returned by default, yet says nothing about embedding inclusion, permission requirements, or what happens for a nonexistent ID.

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 with zero filler; the resource and the returned content are stated up front and nothing is repeated.

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 single-record lookup with fully documented parameters and no output schema, the description gives an adequate sense of what is returned (particle group plus child quantum states). Only error/absence behavior and the optional embedding payload are left unaddressed.

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 100%, so all three parameters, including defaults for include_embedding and include_quantum_states, are already documented in structured data. The description only echoes the quantum-states inclusion and adds no format, range, or semantics beyond the schema, so the baseline 3 applies.

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?

"Retrieve details of a single subatomic particle" is a specific verb plus resource, and "single" distinguishes it from list_subatomic_particles. It also names the content scope (particle group, child quantum states), so an agent knows what it gets back.

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?

There is no explicit when-to-use, when-not-to-use, or named alternative. The single-resource framing implicitly contrasts with the list tool, but the agent is left to infer that a get-by-id is required rather than a list-and-filter, and no prerequisite or failure condition (e.g., unknown ID) is mentioned.

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