Skip to main content
Glama

get_quantum_state

Retrieve a single quantum state by ID with parent subatomic particle and particle group metadata, plus an optional 1024-float vector embedding.

Instructions

Retrieve details of a single quantum state including parent subatomic particle and particle group metadata.

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_quantum_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesQuantum State ID
include_embeddingNoInclude raw 1024-float vector embedding

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?

With no annotations, the description carries the full burden for behavioral disclosure. 'Retrieve' implies a read, and the returned metadata fields are listed, but nothing is said about behavior when the ID does not exist, permission requirements, or that include_embedding produces a large 1024-float payload. That leaves meaningful behavioral gaps for a no-annotation tool.

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 the verb first and the returned content after; nothing is wasted. It is short enough that it could have afforded one clause of usage guidance.

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 simple two-parameter read with no output schema, the description conveys what the record contains, which partially substitutes for a missing output schema. It is still silent on error behavior and on the cost of including the embedding, so it is adequate rather than complete.

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%, with both 'id' and 'include_embedding' documented including the embedding vector size and default. Baseline is 3; the description adds no parameter-level meaning beyond calling out which related metadata appears in the result.

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 ('Retrieve') and resource ('a single quantum state'), and enumerates the included data (parent subatomic particle, particle group metadata). The word 'single' implicitly contrasts it with list_quantum_states, but no sibling is named explicitly.

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?

The description gives no when-to-use guidance, no prerequisites, and does not name list_quantum_states as the alternative for multiple records. An agent must infer from the word 'single' that this is the by-ID lookup path.

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