Skip to main content
Glama

find_counterparts

Finds nearest astrophysical counterparts for a star system or celestial body using 1024-dimensional vector cosine distance, with optional filters by star system or cosmic structure.

Instructions

Find nearest astrophysical counterparts to a specified star system or celestial body 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 star system or celestial body
limitNoNumber of nearest neighbors to return (default: 10)
entity_typeYesEntity type to find counterparts for: star_system or celestial_body
star_system_idNoOptional star system ID to filter counterpart candidates (for celestial body counterparts)
include_embeddingNoWhether to include raw 1024-float vector embeddings in results
cosmic_structure_idNoOptional cosmic structure (galaxy/cluster) ID to filter counterpart candidates

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?

No annotations are provided, so the description carries the full burden. It does add genuine behavioral context by disclosing the similarity metric and index type ('1024-dimensional pgvector cosine distance'), which tells the agent how ranking works. However, it omits the read-only nature, the precondition of a pre-computed embedding, behavior on missing embeddings, and anything about result ordering or pagination.

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 purpose appears before the technical mechanism, and the pgvector detail is compact rather than redundant. Nothing in it could be removed without losing information.

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 six parameters, no annotations, and no output schema, the description covers purpose and scoring method but leaves gaps an agent would care about: whether embeddings must be pre-generated, how optional filters (star_system_id, cosmic_structure_id) combine with entity_type, and what a result item contains. Adequate but not complete for a tool of this complexity.

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 every one of the six parameters is already documented in the schema, including the entity_type enum and the optional filter IDs. The description's phrase 'a specified star system or celestial body' merely restates the entity_type enum values and adds no format, default, or interaction semantics beyond the schema. 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 specific verb ('Find nearest astrophysical counterparts') and a concrete resource scope ('a specified star system or celestial body'), plus the similarity mechanism. It is clearly distinguishable from the get_*/list_* siblings, which retrieve by ID rather than by similarity. It stops short of naming a sibling or stating a boundary, so 5 is not warranted.

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?

Use is implied by 'Find nearest counterparts', but the description never states when to prefer this over get_star_system/get_celestial_body, nor any precondition. The presence of generate_star_system_embedding and generate_celestial_body_embedding siblings suggests embeddings must exist first, yet the description says nothing about that dependency or what happens if an embedding is missing.

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