Skip to main content
Glama

find_counterparts

Find nearest cross-cultural mythological counterparts for a god or myth using vector similarity across world pantheons, with optional pantheon filtering and result limits.

Instructions

Find nearest mythological counterparts to a specified god or myth using pgvector cosine distance across world pantheons.

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 god or myth
limitNoNumber of nearest neighbors to return
entity_typeYesEntity type to find counterparts for: god or myth
pantheon_idNoOptional pantheon ID to filter counterpart candidates (for god counterparts)
include_embeddingNoWhether to include raw 1024-float vector embeddings in results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It usefully discloses the similarity metric (cosine distance) and that results are nearest neighbors, but it says nothing about whether an embedding must already exist, what happens when one is missing, result ordering/ties, or the cost of the vector scan. For an unannotated retrieval tool this leaves key behavioral questions unanswered.

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 sentence, front-loaded with the action and scope, with zero filler. Every clause (target, mechanism, scope) contributes 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?

For a five-parameter similarity-search tool with a fully documented schema and no output schema, the description covers purpose and mechanism but not the prerequisites or result characteristics an agent needs to call it successfully. It is adequate but has a clear behavioral gap around embedding availability and return contents.

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 parameter is already documented, including the god/myth enum, limit bounds, pantheon_id filter, and include_embedding. The description adds no parameter-level meaning beyond the schema (e.g., how entity_type interacts with id or how pantheon_id narrows candidates), so the baseline 3 applies.

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?

States a specific verb ('find nearest counterparts'), the target resource ('a specified god or myth'), and the scope ('across world pantheons') with the underlying mechanism (pgvector cosine distance). This is clearly distinct from sibling tools like compute_clusters or get_god, so an agent can select it without opening the schema.

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 phrasing ('counterparts to a specified god or myth'), but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as compute_clusters for grouping rather than similarity lookup. It also omits the likely prerequisite that the entity already has an embedding generated via the sibling embedding tools.

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