Skip to main content
Glama

update_subatomic_particle

Update an existing subatomic particle's attributes by ID, including its name, themes, description, or particle group assignment.

Instructions

Update an existing subatomic particle's attributes.

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

Input Schema

NameRequiredDescriptionDefault
idYesSubatomic Particle ID
nameNoUpdated subatomic particle name
themesNoUpdated physical themes
descriptionNoUpdated description
particle_group_idNoReassign to another Particle Group ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 behavioral burden and does not meet it. It never says whether this is a partial update (are omitted fields preserved or cleared?), whether it errors on unknown IDs, or what permissions are required for a mutation.

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 core action front-loaded, though the brevity comes at the cost of substance rather than being earned through efficient information density.

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 five-parameter mutation tool with no annotations and no output schema, the definition is far too thin. An agent cannot tell whether updates are partial or full-replacement, nor what the response contains after a successful 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?

Schema description coverage is 100%, so all five fields including 'id' and 'particle_group_id' are already documented in the schema. The description adds no semantics 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.

Purpose3/5

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

The description names a verb (update) and resource (subatomic particle) but 'attributes' is generic and the sentence largely restates the tool name. It does signal that the particle must already exist, which separates it from create_subatomic_particle, but nothing distinguishes it from upsert_subatomic_particles_batch or the populate_* siblings.

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 when-to-use guidance, no mention of when to prefer a batch upsert or populate variant, and no prerequisites such as needing a valid existing ID. The agent must infer all routing decisions from sibling names alone.

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