Skip to main content
Glama

find_counterparts

Find nearest physical counterparts or symmetry analogs to a subatomic particle or quantum state using 1024-dimensional cosine distance to support physics comparisons.

Instructions

Find nearest physical counterparts or symmetry analogs to a specified subatomic particle or quantum state using 1024-dimensional pgvector cosine distance.

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": {
      "entity_type": "<entity_type>",
      "id": "<id>"
    },
    "name": "find_counterparts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID of the subatomic particle or quantum state
limitNoNumber of nearest neighbors to return (default: 10)
entity_typeYesEntity type to find counterparts for: subatomic_particle or quantum_state
include_embeddingNoWhether to include raw 1024-float vector embeddings in results
particle_group_idNoOptional particle group ID to filter counterpart candidates
subatomic_particle_idNoOptional subatomic particle ID to filter counterpart candidates (for quantum state counterparts)

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, the description carries the full behavioral burden. It usefully discloses the similarity method and vector dimensionality, but it does not state whether the operation is read-only, what result ordering is used, whether results are paginated, or what return structure to expect.

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?

The definition is a single front-loaded sentence with no filler, and it efficiently combines the action, target, entity types, and similarity method. Every phrase contributes to identifying what the tool does.

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?

The input schema is rich and the description covers the core purpose and metric, but the tool has no annotations and no output schema. The description therefore leaves important context unspecified, including result format, ordering, prerequisites, and the read-only or mutation profile.

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 the input schema already documents all six parameters in detail. The description adds method context ('1024-dimensional pgvector cosine distance') but does not clarify the optional filters, limit behavior, or embedding inclusion beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Find'), a concrete target ('nearest physical counterparts or symmetry analogs'), named entity types ('subatomic particle or quantum state'), and a distinct method ('1024-dimensional pgvector cosine distance'). Together these make the tool's operation distinguishable from CRUD, listing, and embedding-generation siblings even though no sibling is explicitly named.

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?

The description implies the basic use case by saying what it finds, but it gives no explicit when-to-use guidance, no conditions for choosing it over related tools, and no prerequisites such as whether embeddings must already exist. It also does not say when not to use it or how optional filters affect candidate selection.

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