Skip to main content
Glama

create_quantum_state

Creates a quantum state or eigenmode for a specified subatomic particle, letting you define its name, quantum numbers, thematic tags, and parent particle.

Instructions

Create a new quantum state or eigenmode under a subatomic particle.

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": {
      "subatomic_particle_id": "<subatomic_particle_id>",
      "name": "<name>"
    },
    "name": "create_quantum_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesQuantum state name (e.g. 'Helicity +1/2 Right-Handed', 'Color Singlet', 'Ground Eigenstate')
themesNoThematic tags (e.g. ['spin-projection', 'chirality', 'eigenmode'])
descriptionNoQuantum numbers, projection eigenvalues, wavefunctions, and symmetry representations
subatomic_particle_idYesParent Subatomic Particle ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full burden of behavioral disclosure, yet it says nothing about permissions, idempotency, duplicate-name handling, or what is returned on success. For a mutation tool with zero annotation coverage, this is a substantial gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity reflects under-specification rather than disciplined concision.

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

Completeness2/5

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

With four parameters, no output schema, and no annotations, the one-line description leaves an agent without the operational context needed to call it confidently — notably whether the parent particle must exist and how duplicates are treated. The rich schema offsets this only partially.

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%, and the schema already explains name, themes, description, and subatomic_particle_id with examples, so the baseline is 3. The description adds no meaning beyond that — it does not clarify the parent-child constraint or how themes interact with name.

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?

The description names a specific verb and resource ('Create a new quantum state or eigenmode') and scopes it to a parent ('under a subatomic particle'), which separates it from create_subatomic_particle and from batch siblings like upsert_quantum_states_batch. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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 statement of when to use this versus alternatives such as upsert_quantum_states_batch, populate_quantum_states_bulk, or update_quantum_state, and no prerequisites (e.g. that the parent particle must already exist). Usage is only implied by the verb 'Create'.

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