Skip to main content
Glama

update_particle_group

Update an existing particle group's name or description by ID, letting AI agents revise physics model metadata through the Physicist MCP Server.

Instructions

Update an existing particle group's name or description.

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

Input Schema

NameRequiredDescriptionDefault
idYesParticle Group ID
nameNoUpdated particle group name
descriptionNoUpdated description

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 provided, so the description carries the full burden. It doesn't disclose partial-update semantics (does omitting name/description leave values untouched, or clear them?), whether the operation is reversible, permission requirements, or what the response contains — all important for a mutation 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 no filler or redundancy. Brevity is a virtue here, but the same length could have been used to add the partial-update rule that's currently missing.

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?

The tool is simple (3 params, full schema coverage, no output schema), so little is needed; however, as an unannotated mutation, the definition should at minimum clarify partial-update behavior and required permissions to be 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 coverage is 100%, so id, name, and description are already documented in the schema; the description only restates that name and description are the updatable fields. Baseline 3 applies since the schema does the heavy lifting, though it does confirm both are optional updates.

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?

States a specific verb ('Update') and resource ('particle group'), plus the fields in scope (name or description). The resource name distinguishes it from siblings like update_subatomic_particle and create_particle_group, though no explicit sibling contrast is written.

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?

'existing' implies the group must already exist, hinting that create_particle_group is for new ones, but there is no explicit when-to-use, no prerequisites (e.g., required ID, permissions), and no statement of when this tool should be avoided.

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