Skip to main content
Glama

create_particle_group

Creates a new particle group record in the catalog using a required group name and optional taxonomic or symmetry details.

Instructions

Create a new particle group record in the catalog.

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": {
      "name": "<name>"
    },
    "name": "create_particle_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the particle group (e.g. 'Quarks', 'Leptons', 'Gauge Bosons', 'Baryons')
descriptionNoTaxonomic, theoretical, and gauge symmetry 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 behavioral burden, and it only implies mutation via 'Create'. It says nothing about whether the name must be unique, what happens on a duplicate, whether the operation is idempotent, what permissions are needed, or what the call returns.

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 repetition. It is efficient, though the brevity reflects under-specification rather than tight packaging of needed detail.

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 (two params, one required, flat schema, fully documented), so the description is close to adequate. However, as a mutation tool with no annotations and no output schema, it leaves return behavior, duplication handling, and failure modes entirely unspecified.

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%, with the 'name' parameter documented with concrete examples and 'description' explained, so the schema already does the work. The description adds no parameter-level meaning beyond that, which is the baseline expectation when schema descriptions are complete.

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 ('Create') and resource ('particle group record in the catalog'), which is enough to distinguish it from read-side siblings like list_particle_groups or get_particle_group. It stops short of explicitly differentiating it from create_subatomic_particle or upsert_particle_groups_batch, which the agent must resolve on its own.

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?

The description gives no when-to-use guidance, no prerequisites, and no mention of alternatives such as upsert_particle_groups_batch or create_subatomic_particle, despite a crowded create/upsert namespace. Everything about tool selection is left to inference.

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