Skip to main content
Glama

list_subatomic_particles

Retrieve subatomic particles registered in Physicist, filtered by group, theme, embedding status, or keyword search to find relevant particle records.

Instructions

List subatomic particles registered in Physicist with filtering by particle group, themes, embedding status, and search keywords.

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_subatomic_particles"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch query matching subatomic particle name or description
limitNoPagination limit (default: 50)
themeNoFilter subatomic particles containing a specific theme tag
offsetNoPagination offset (default: 0)
embeddedNoFilter by embedding presence (true for embedded only, false for missing)
particle_groupNoFilter subatomic particles by Particle Group name
include_embeddingNoInclude raw 1024-float vector embedding
particle_group_idNoFilter subatomic particles by Particle Group ID
include_quantum_statesNoInclude child quantum states in results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full behavioral burden, and it discloses almost nothing beyond the verb: no statement that results are paginated and ordered how, no warning that include_embedding returns large 1024-float vectors, no note on whether this is a safe read-only operation. "List" weakly implies read-only, but that inference is left entirely to the agent.

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; the resource precedes the filter enumeration, which is the right order for scanning. It is a slightly run-on clause chain, but every element carries information.

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?

With nine optional parameters, no annotations, and no output schema, the description should carry more weight than one sentence. It omits pagination behavior, the cost/size implications of include_embedding and include_quantum_states, and any sense of what a returned particle record contains.

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 all nine parameters are already documented in the schema and the baseline is 3. The description echoes four of them (particle group, theme, embedded, search keywords) without adding syntax, defaults, or interaction rules, and says nothing about limit/offset or the include_* flags.

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?

"List subatomic particles registered in Physicist" gives a specific verb plus resource and immediately enumerates the filter dimensions, so an agent knows this is a filtered enumeration endpoint rather than a single-record fetch or a mutation. It stops short of naming how it differs from the sibling `search` tool, which also exposes a query parameter.

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 filter list implies the intended use case (browse/filter the particle catalog), and the resource naming separates it from siblings like list_particle_groups or list_quantum_states. However, there is no explicit when-to-use or when-not-to-use statement, and nothing says when to prefer this over the `search` sibling for keyword lookups.

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