Skip to main content
Glama

populate_subatomic_particles_bulk

Trigger bulk discovery of subatomic particles across one or all particle groups via background job, optionally limiting to a particle group ID or running synchronously.

Instructions

Bulk trigger discovery of subatomic particles across one or all particle groups via background job.

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

Input Schema

NameRequiredDescriptionDefault
syncNoIf true, run synchronously
particle_group_idNoOptional Particle Group ID to limit subatomic particle discovery

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 at all, the description carries the full behavioral burden; it does disclose the most important trait, that work happens via a background job, and that the operation is bulk. It does not say whether the trigger is idempotent, whether it overwrites existing particles, what identifier or handle is returned, or how the sync flag changes the behavior — significant gaps for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the scope and mechanism both land in the first clause. Nothing is wasted and nothing needs to be re-read.

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 bulk, asynchronous mutation with no annotations and no output schema, the definition is minimal but not empty — the background-job nature is captured. What is missing is how to follow up on the job (a get_job_status sibling exists) and what the call returns, which an agent needs in order to use this 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 description coverage is 100%, so both the sync flag and particle_group_id are already documented in the schema, and the baseline is 3. The description confirms the semantics of particle_group_id ('one or all particle groups') but adds nothing about sync or its interaction with the background-job behavior, so it does not exceed the schema.

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 ('Bulk trigger discovery of subatomic particles') plus the scope ('across one or all particle groups') and the execution model ('background job'). It implicitly distinguishes itself from the single-group sibling 'populate_particle_group_subatomic_particles' via the 'one or all' wording, but never names that sibling, so differentiation is inferential rather than explicit.

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 phrase 'across one or all particle groups' implies when to use this versus a single-group populate call, and the optional particle_group_id is implied by 'one or all'. However, there are no explicit when-to-use or when-not-to-use statements, and no guidance about when to set sync versus accepting a background job.

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