Skip to main content
Glama

get_particle_group

Retrieve details for a particle group by ID, including its subatomic particles when requested. Use it to inspect group composition and related particle data.

Instructions

Retrieve details of a single particle group including its subatomic particles.

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

Input Schema

NameRequiredDescriptionDefault
idYesParticle Group ID
include_subatomic_particlesNoInclude subatomic particles belonging to this particle group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 burden; "Retrieve" does signal a read-only operation and it discloses that the response can include subatomic particles. It says nothing about not-found behavior, permissions, or what changes when include_subatomic_particles is set false, so disclosure is partial rather than complete.

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 the core action front-loaded and no filler. It is arguably too terse for a tool with no annotations, but nothing in it is wasted.

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 simple two-parameter getter with full schema coverage this covers the essentials. However, with no output schema, the phrase "details ... including its subatomic particles" is the only statement of return shape and remains vague about what fields come back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented and the baseline is 3. The description adds a bit beyond the schema by tying the returned payload to the subatomic particles, reinforcing that the boolean toggle affects response contents rather than a filter.

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 ("Retrieve") and a scoped resource ("a single particle group"), which implicitly separates it from list_particle_groups and from the create/update/delete siblings. It never names an alternative, so the differentiation is inferred from wording rather than stated.

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?

Usage is only implied: "single particle group" suggests ID-based lookup as opposed to listing, but the description never says when to prefer this over list_particle_groups or get_subatomic_particle, nor any preconditions such as the ID needing to exist.

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