Skip to main content
Glama

upsert_species_batch

Insert or update multiple species in a biome by name with case-insensitive matching, creating new entries or refreshing existing ones in one batch.

Instructions

Batch insert or update species scoped to a specific biome 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": {
      "biome_id": "<biome_id>",
      "species": "<species>"
    },
    "name": "upsert_species_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
speciesYesArray of species entries to upsert
biome_idYesParent Biome ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key upsert trait: entries are matched to existing species case-insensitively on name, so this creates-or-updates rather than blindly appending. It is silent on what happens to fields omitted on an update (e.g. themes), whether values are replaced or merged, transaction/partial-failure behavior for the batch, and required authorization.

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 scope and matching semantics front-loaded and no filler. Every clause earns its place and nothing is repeated from the schema.

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 tool with a fully documented schema, no output schema, and no annotations, this covers the core what-and-how adequately. It falls short of complete by omitting return shape (created vs. updated counts) and batch-failure semantics, which matter for an upsert.

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 coverage is 100%, so the baseline is 3, but the description earns above baseline by explaining that biome_id scopes the operation and that name is the case-insensitive match key rather than just a label field. It still adds nothing about what description or themes mean on an update path.

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 states a specific verb pair (batch insert or update), the resource (species), the scope (a specific biome), and the identity key (case-insensitive name match). That sets it apart from single-record siblings like create_species and update_species implicitly through 'batch', though no sibling is named explicitly.

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?

Nothing says when to prefer this over create_species, update_species, or populate_species_bulk. The word 'batch' hints at bulk usage, but there is no explicit trigger condition, prerequisite, or exclusion to route an agent between the upsert and populate variants.

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