Skip to main content
Glama

find_counterparts

Finds nearest ecological counterparts or convergent evolutionary analogs for a species or organism using 1024-dimensional cosine similarity, with optional limit and distance threshold.

Instructions

Find nearest ecological counterparts or convergent evolutionary analogs to a specified species or organism 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 species or organism
limitNoNumber of nearest neighbors to return (default: 10)
thresholdNoMaximum cosine distance threshold
entity_typeYesEntity type to find counterparts for: species or organism

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 supplied, so the description carries the full behavioral burden. It does disclose the ranking semantics (cosine distance over 1024-dim embeddings), which goes beyond a bare restatement, but it omits whether the lookup is read-only, what happens if no embedding exists, how results are ordered, and whether threshold filtering is inclusive or exclusive.

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 comes first and the technical qualifier (vector dimensionality and metric) is appended where it clarifies rather than obscures.

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 description covers the core intent but leaves the agent guessing on prerequisites and result shape. It also does not clarify the domain distinction between an 'ecological counterpart' and a 'convergent evolutionary analog', which is the key semantic ambiguity in the tool's own phrasing.

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 baseline is 3. The description's mention of 'cosine distance' does add interpretive meaning to the otherwise bare 'threshold' parameter (a maximum cosine distance, consistent with the 0-2 bound), but it adds nothing about limit, entity_type, or the id scoping.

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 names a specific verb ('Find') and a precise resource ('nearest ecological counterparts or convergent evolutionary analogs') for a specified species or organism, and adds the mechanism (1024-dimensional pgvector cosine distance). It is clearly distinguishable in intent from CRUD siblings like get_species or create_organism, though it does not explicitly contrast itself with similarity-adjacent siblings such as compute_clusters.

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 implied by the phrase 'nearest ecological counterparts' - an agent can infer this is the similarity-search tool - but there is no explicit when-to-use guidance, no statement of prerequisites (e.g., that an embedding must already exist, presumably via generate_species_embedding/generate_organism_embedding), and no named alternatives or exclusions.

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