Skip to main content
Glama

list_quantum_states

Retrieve quantum states and eigenmodes with filters for subatomic particle, particle group, theme, search query, and embedding status to locate relevant physics records.

Instructions

List quantum states and eigenmodes registered in Physicist with filtering by subatomic particle, particle group, themes, and embedding status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_quantum_states"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch query matching quantum state name or description
limitNoPagination limit (default: 50)
themeNoFilter by quantum state or symmetry theme tag
offsetNoPagination offset (default: 0)
embeddedNoFilter by embedding presence (true for embedded only, false for missing)
include_embeddingNoInclude raw 1024-float vector embedding
particle_group_idNoFilter by parent Particle Group ID
subatomic_particle_idNoFilter by parent Subatomic Particle ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'List' implies a read-only, non-destructive operation and identifies the backing system ('Physicist'), but it says nothing about pagination behavior, default/maximum page size, result truncation, ordering, or the fact that include_embedding returns a large 1024-float vector.

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 is partly the source of the gaps in the other dimensions rather than a virtue in itself.

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

Completeness3/5

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

For a read-only list tool with eight optional parameters, no annotations, and no output schema, the description covers the filtering surface adequately. It leaves unclear what is actually returned (are eigenmodes included in results?), how paging works, and what include_embedding does to the payload.

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 each parameter is already documented in the schema, which sets the baseline at 3. The description restates the filterable categories (particle, particle group, theme, embedding status) but adds no semantics beyond the schema and omits q, limit, offset, and include_embedding entirely.

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?

Uses a specific verb ('List') with a specific resource ('quantum states and eigenmodes') and names the filterable dimensions, so an agent can distinguish it from get_quantum_state (single-item) and create/delete/update siblings without opening the schema. It stops short of explicitly naming which sibling to prefer for retrieval of a single record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the enumerated filter dimensions: an agent can infer this is the tool for browsing/filtering the registry rather than fetching one record. However, there is no explicit statement of when to use this versus 'get_quantum_state' or 'populate_quantum_states_bulk', and no stated prerequisites.

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