Skip to main content
Glama

upsert_organisms_batch

Batch insert or update organisms for a specific species, matching existing records by name case-insensitively to avoid duplicates.

Instructions

Batch insert or update organisms scoped to a specific species matching case-insensitively on name.

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": {
      "species_id": "<species_id>",
      "organisms": "<organisms>"
    },
    "name": "upsert_organisms_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
organismsYesArray of organism entries to upsert
species_idYesParent Species ID

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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the upsert key (case-insensitive name within a species), which is genuinely useful, but it is silent on whether omitted fields like themes are preserved or wiped on update, on partial-failure/atomicity behavior for a batch call, and on permission requirements.

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 dense sentence with the operation and its two scoping constraints front-loaded. Nothing is repeated from the schema and no words are wasted.

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 two-parameter mutation with no annotations and no output schema, the definition covers the matching semantics but leaves the agent guessing about return values (ids? counts?), conflict resolution, and error behavior on a partially invalid batch. Adequate but with real gaps for a write tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, and the description earns an upgrade by explaining that 'name' functions as the case-insensitive match key for deciding insert versus update — semantics the schema does not convey. It does not clarify how nested 'themes' are treated on update.

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 uses a specific verb pair (batch insert or update) with a clear resource (organisms) and adds two distinguishing qualifiers: scope to a species and case-insensitive name matching. It implicitly separates itself from single-record siblings like create_organism and from read siblings like list_organisms, but it never names an alternative explicitly.

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 word 'batch' and 'insert or update' imply the use case (bulk loading many organisms rather than one at a time), but there is no explicit statement of when to prefer this over populate_organisms_bulk or create_organism, and no stated prerequisites such as the species needing to exist first.

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