Skip to main content
Glama

delete_subatomic_particle

Deletes a subatomic particle by ID and removes its cascaded quantum states, keeping physics model data consistent.

Instructions

Delete a subatomic particle and its cascaded 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": "delete_subatomic_particle"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSubatomic Particle ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does provide genuinely useful behavioral information — that deletion cascades to dependent quantum states, which an agent could not infer from the schema — but it omits irreversibility, permission requirements, and what happens on failure, all material for a destructive operation.

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?

One sentence, front-loaded with the action and resource, with no filler or redundancy. The cascade clause earns its place by conveying scope.

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 destructive, annotation-free tool with no output schema, the description covers what is deleted but not the consequences: reversibility, authorization, error behavior, or the resulting state. The cascade note helps, but an agent still lacks enough to invoke this confidently in edge cases.

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?

With a single required parameter and 100% schema description coverage, the schema already explains that 'id' is the subatomic particle ID to delete. The description adds no format, range, or validity nuance beyond that, so the baseline of 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 names a specific verb ('Delete') and resource ('a subatomic particle'), and adds a scope detail that the cascade of quantum states is removed too. It does not distinguish itself from sibling delete tools such as delete_quantum_state or delete_particle_group, so an agent must infer the boundary from names alone.

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 or when-not-to-use guidance, no mention of prerequisites, and no pointer to an alternative such as delete_quantum_state for removing states individually. Usage is only implied by the verb and resource name.

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