Skip to main content
Glama

upsert_biomes_batch

Batch insert or update biomes by case-insensitive name matching to avoid duplicate records and keep ecological data current.

Instructions

Batch insert or update biomes 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": {
      "biomes": "<biomes>"
    },
    "name": "upsert_biomes_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
biomesYesArray of biomes to upsert

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?

With no annotations, the description carries the full behavioral burden. It usefully discloses the case-insensitive name match that drives insert-vs-update, but leaves out what an update actually does to an existing record (full replace vs. merge of description), whether the batch is atomic or partial-failure tolerant, and what permissions are required for a write operation.

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?

One sentence, front-loaded with the operation type, with zero filler. The matching rule is included in the same breath as the action, which is exactly where it matters.

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?

This is a batch mutation tool with no annotations and no output schema, so the description is the only source of behavioral detail. It omits the outcome contract (counts of inserted vs. updated, behavior on duplicates within the same batch) and failure semantics, which an agent needs before committing a batch write.

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% and there is a single array parameter already documented in the schema, so the baseline applies. The description adds real meaning by stating that matching is case-insensitive on name, but it does not clarify how the description field is treated 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 names a specific verb pair (batch insert or update) and resource (biomes), plus the matching key. It is clearly distinguishable from list_biomes or create_biome without opening the schema, though it does not explicitly name those siblings.

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?

Implied usage is clear — use this when applying many biomes at once and deduplicating by name rather than issuing individual create_biome calls. However, there is no explicit statement of when to prefer it over create_biome or populate_biomes, and no exclusions or prerequisites.

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