Skip to main content
Glama

create_subatomic_particle

Create a new subatomic particle record in Physicist under a specified particle group, including name, themes, and physical properties for querying and synthesis.

Instructions

Create a new subatomic particle record in Physicist.

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

Input Schema

NameRequiredDescriptionDefault
nameYesSubatomic particle name (e.g. 'Proton', 'Muon', 'Higgs Boson', 'Top Quark')
themesNoPhysical or symmetry theme tags (e.g. ['hadron', 'fermion', 'baryon', 'valence-uud'])
descriptionNoPhysical properties, gauge invariants, rest mass, decay modes, and spin
particle_group_idYesParent Particle Group ID

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?

With no annotations supplied, the description carries the full burden of behavioral disclosure and delivers almost none. It does not say whether creation requires an existing parent group, what happens on a duplicate name within a group, whether the operation is idempotent, or what identifier comes back on success.

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 zero filler. It is efficient, though the brevity reflects under-specification rather than disciplined trimming.

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 four-parameter mutation tool with no annotations and no output schema, the description is too thin: it omits return behavior, duplicate handling, and the parent-group relationship between the two required fields. An agent would have to guess at failure modes before calling it.

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 every parameter (name, themes, description, particle_group_id) is already documented with examples and constraints in the schema. The description adds no meaning beyond that, which is the baseline 3 case when the schema does the heavy lifting.

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 ('subatomic particle record') plus the target system ('Physicist'), so the operation is unambiguous. It does not distinguish itself from siblings such as create_particle_group, upsert_subatomic_particles_batch, or update_subatomic_particle, which is the only thing keeping it from a 5.

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?

No guidance on when to use this versus update_subatomic_particle or upsert_subatomic_particles_batch, and no mention of preconditions like the parent particle_group_id needing to exist. 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.