Skip to main content
Glama

generate_species_embedding

Generates or refreshes a 1024-dimensional semantic embedding for a species, enabling semantic search and comparison based on species data.

Instructions

Generate or refresh the 1024-dimensional semantic embedding for a species.

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

Input Schema

NameRequiredDescriptionDefault
idYesSpecies ID
syncNoIf true, wait synchronously for embedding generation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 of behavioral disclosure. It reveals the embedding dimension and that an existing embedding can be refreshed, but omits side effects, idempotency, permissions, cost, and what happens when 'sync' is false.

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. Each element—action, embedding dimensionality, and target resource—earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a generation tool with no annotations and no output schema, important context is missing. The description does not explain whether 'sync=false' enqueues an asynchronous job, what the response contains, or whether regeneration overwrites existing vectors.

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 coverage is 100%, and both 'id' and 'sync' are documented in the input schema, so the baseline is 3. The description adds the embedding dimensionality and 'refresh' semantics but does not clarify how 'sync' changes execution or return behavior.

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 ('Generate or refresh'), a specific resource ('species'), and the output ('1024-dimensional semantic embedding'). The species scope clearly separates it from sibling tools such as generate_organism_embedding.

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?

The phrase 'Generate or refresh' implies use when an embedding is missing or stale, but the definition gives no explicit when-to-use guidance. It does not name alternatives such as generate_organism_embedding or state when this tool should be avoided.

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