Skip to main content
Glama

trigger_bulk_embeddings

Enqueue bulk embedding generation for all Species or Organism records, optionally restricting processing to records that are not yet embedded.

Instructions

Enqueue bulk embedding generation for all Species or Organisms.

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": {
      "model_type": "<model_type>"
    },
    "name": "trigger_bulk_embeddings"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_typeYesEntity type to generate embeddings for: Species or Organism
only_missingNoIf true, only generate embeddings for records that are not yet embedded

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 behavioral burden, yet it only implies asynchrony via the word 'Enqueue'. It says nothing about what is returned (presumably a job handle), whether progress is tracked via get_job_status, cost/duration implications of a bulk run, permission requirements, or what happens to existing embeddings when only_missing 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity borders on under-specification for an asynchronous bulk operation.

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 is the only place an agent could learn about job handles, progress tracking, or side effects, and it covers none of these. For a bulk enqueue operation with real side effects on stored embedding data, this is too thin.

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 model_type (enum) and only_missing (default true) fully documented in the schema, so the baseline of 3 applies. The description adds no syntax, format, or default-relevant nuance beyond what the schema already states.

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?

States a specific verb ('Enqueue'), a specific resource ('bulk embedding generation'), and a scope ('all Species or Organisms'), so an agent knows this is a batch operation rather than a single-record one. It does not explicitly name the single-record siblings (generate_species_embedding / generate_organism_embedding), leaving the batch-vs-single distinction implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of when not to use it, and no pointer to alternatives such as the single-entity embedding tools. An agent must infer entirely on its own that this is the choice for full-corpus backfills.

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