Skip to main content
Glama

delete_particle_group

Deletes a particle group by ID and removes its cascaded subatomic particles and quantum states, keeping physics models consistent.

Instructions

Delete a particle group and its cascaded subatomic particles and 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_particle_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesParticle Group ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full safety burden and does provide the crucial warning that subatomic particles and quantum states are also deleted. It still omits reversibility, authorization or confirmation needs, and behavior for invalid or nonexistent IDs, leaving the operational picture incomplete.

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 front-loaded sentence states the action, target, and cascading side effect without filler. Its length is appropriate for a single-parameter operation.

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

Completeness4/5

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

For a simple one-parameter deletion, the schema and cascade warning provide enough information to identify the target and understand the principal side effect. The absence of annotations and an output schema leaves some operational and response details undisclosed, preventing a top completeness score.

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?

The sole id parameter is already fully documented in the schema, including its type and role, so the baseline score applies. The description adds no further ID semantics, constraints, or guidance on obtaining an ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description supplies a specific verb and resource, and its cascade scope distinguishes the operation from sibling tools that delete only a subatomic particle or quantum state. It is clear that the top-level target is a particle group and that deletion extends beyond that group.

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?

The cascade wording implies use when an entire group and its associated subatomic particles and quantum states should be removed. It gives no explicit when-not guidance, prerequisites, or pointer to a narrower deletion alternative.

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