Skip to main content
Glama

search

Find subatomic particles and quantum states across catalogs via semantic or keyword queries, filtering by entity type and result count.

Instructions

Unified cross-catalog semantic or keyword search across subatomic particles and quantum states in the Physicist comparative physics manifold.

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

Input Schema

NameRequiredDescriptionDefault
qYesSearch query text (e.g. 'heavy gauge boson with electroweak coupling', 'color-singlet ground state baryon')
modeNoSearch mode: semantic (pgvector cosine similarity), keyword (text matching), or autoauto
limitNoMaximum number of results to return (1-100)
target_typeNoFilter search results by entity type: all, subatomic_particle, or quantum_stateall

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 carries the full behavioral burden, and it discloses little. It does not state that the operation is a read-only retrieval, how results are ranked or scored, whether truncated result sets are signaled, or what shape the response takes. The semantic/keyword distinction it mentions is already fully expressed by the schema's mode enum.

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

Conciseness3/5

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

It is a single sentence with the core purpose front-loaded, which is good structure. However, the tail phrase 'in the Physicist comparative physics manifold' is filler that does not help an agent decide or invoke, and the sentence tries to cover both scope and modality at once.

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?

With four parameters fully documented in the schema and no output schema, the main gaps are behavioral: no routing guidance relative to the many sibling retrieval tools, no note on result ordering or volume. It is minimally sufficient to invoke correctly but not sufficient to choose confidently.

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%, with every parameter (q, mode, limit, target_type) documented including enums and defaults, so the schema does the heavy lifting. The description adds no syntax hints, query-construction advice, or interaction between mode and target_type, so baseline 3 applies.

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 clear verb+resource: a 'unified cross-catalog semantic or keyword search across subatomic particles and quantum states'. That distinguishes it from single-entity siblings like get_subatomic_particle and list_* tools. It stops short of 5 due to the trailing 'Physicist comparative physics manifold' phrasing, which adds branding rather than precision.

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?

Usage is only implied by the word 'search' and by 'cross-catalog', which suggests it is the multi-entity discovery path. There is no explicit statement of when to prefer this over get_subatomic_particle, get_quantum_state, or list_* siblings, and no guidance on when semantic vs keyword mode is appropriate.

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