Skip to main content
Glama

delete_quantum_state

Removes a quantum state from the catalog by its ID, enabling agents to manage physics domain models in the Physicist MCP Server.

Instructions

Delete a quantum state from the catalog.

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": "delete_quantum_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesQuantum State ID to delete

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 carries the full burden of behavioral disclosure. 'Delete ... from the catalog' hints at removal from a listing, but it does not say whether the deletion is permanent or reversible, what happens to embeddings or cluster associations referencing the state, or what the response confirms. For an unannotated destructive mutation this is a significant 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 short sentence with no filler and the destructive action front-loaded. It is efficient, though its brevity is the same brevity that leaves behavioral context missing.

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?

For a destructive single-record mutation with no annotations and no output schema, the description should address irreversibility, side effects on dependent data, and confirmation of success. None of that is present, leaving the agent under-informed before an irreversible call.

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?

Only one parameter exists and schema description coverage is 100%, with the schema already documenting 'Quantum State ID to delete' plus positivity and safe-integer bounds. The description adds no further meaning such as where the ID is obtained, 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?

The description states a specific verb ('Delete') and a specific resource ('a quantum state from the catalog'), which is enough to distinguish it from siblings that delete other resource types such as delete_cluster_report or delete_particle_group. It stops short of differentiating it from a bulk or batch deletion path, but the core purpose is unambiguous.

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 guidance on when to use this instead of update_quantum_state (e.g., to retire rather than remove) or the bulk populate/upsert variants. No prerequisites, no mention of required permissions or confirmation steps, and no exclusions.

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