Skip to main content
Glama

list_particle_groups

Retrieve registered particle groups—taxonomic families, structural sectors, and supermultiplets—with subatomic particle counts; filter by name or description and paginate results.

Instructions

List particle groups (taxonomic families, structural sectors, supermultiplets) registered in Physicist with subatomic particle counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_particle_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFilter particle groups by name or description substring
limitNoPagination limit (default: 50)
offsetNoPagination offset (default: 0)
include_subatomic_particlesNoInclude subatomic particles associated with each particle group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden. 'List ... registered in Physicist with subatomic particle counts' establishes this is a read-only enumeration and hints at the payload contents, but it says nothing about pagination behavior, default result size, or whether the count field is computed versus truncated by the limit.

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 the resource first and the qualifying detail in parentheses; every clause carries information. It could be sharper by trading one of the three parenthetical examples for a concrete usage note, but there is no filler.

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 four-optional-parameter list tool with no annotations and no output schema, the description identifies what is listed and roughly what comes back, and the schema covers all inputs. What is missing is pagination guidance and any statement of result ordering or total-count behavior, which an agent would need to page correctly.

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 q, limit, offset, and include_subatomic_particles are all documented in the schema and the baseline of 3 applies. The phrase 'with subatomic particle counts' loosely gestures at the include_subatomic_particles option but adds no filtering or pagination semantics beyond what the schema already states.

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?

The description gives a specific verb and resource ('List particle groups') and even glosses the domain term with concrete examples (taxonomic families, structural sectors, supermultiplets) plus the returned metric (subatomic particle counts). It is clearly distinguishable from get_particle_group or list_subatomic_particles by the plural list semantics, though no sibling is named explicitly.

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?

The 'List' verb implies a bulk-retrieval use case as opposed to a single-record get, and the mention of counts implies a summarizing overview. However, there is no explicit when-to-use guidance, no mention of when to prefer get_particle_group or list_subatomic_particles, and no stated prerequisites.

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