Skip to main content
Glama

generate_organism_embedding

Generate or refresh a 1024-dimensional semantic embedding for an individual organism, enabling semantic search and clustering by organism ID.

Instructions

Generate or refresh the 1024-dimensional semantic embedding for an individual organism.

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_organism_embedding"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrganism ID
syncNoIf true, wait synchronously for embedding generation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It never discloses cost/latency of generation, whether an existing embedding is overwritten or versioned, what permissions are required, or what the response contains; 'refresh' hints at replacement but nothing more.

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 operation and its scope are stated in the first few words and the dimensionality detail is compaction-friendly context.

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?

With no annotations and no output schema, the description should explain what comes back and what happens on the async path. Because sync defaults to true, an agent that sets sync=false has no guidance about the resulting job or the get_job_status sibling, leaving a real operational gap.

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%, with both 'id' and 'sync' documented in-schema, so the baseline is 3. The description adds nothing about parameter behavior — notably it does not explain the consequence of sync=false, which is the least self-evident parameter.

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?

Specific verb pair ('generate or refresh') plus a precise resource: a 1024-dimensional semantic embedding for an individual organism. The word 'individual' implicitly separates it from generate_species_embedding, but no sibling is named, so the differentiation is suggestive rather than explicit.

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?

'Generate or refresh' implies the two cases where this is appropriate — the embedding is missing or stale — but the description never states prerequisites, when to prefer this over generate_species_embedding, or whether re-running on an already-embedded organism is safe.

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