Skip to main content
Glama

update_biome

Modify an existing biome's name or description by ID to keep ecological records current.

Instructions

Update an existing biome's name or description.

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": "update_biome"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBiome ID
nameNoUpdated biome name
descriptionNoUpdated description

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 burden. It does not disclose whether the update is partial (fields omitted stay unchanged), whether it requires elevated permissions, whether changes are reversible, or what happens when neither name nor description is provided alongside the required id. For a mutation tool with zero annotation coverage this is a real gap.

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 efficient sentence with no filler, front-loaded with the verb and resource. It is terse to the point of omitting useful semantics, but nothing in it is 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?

The tool is simple, all three parameters are schema-documented, and there is no output schema to explain. However, with no annotations the description should still cover partial-update behavior and failure modes, which it omits, leaving it only minimally adequate.

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 coverage is 100%, so the schema already documents id, name, and description; the description adds nothing beyond confirming that name and description are the updatable fields. It does not clarify optionality semantics (that only one of the two must be supplied) or the ID lookup requirement, so the baseline 3 applies.

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 (update) and resource (an existing biome) plus the fields it touches (name, description), so the agent knows exactly what the tool does. It offers no differentiation from siblings such as update_species or create_biome, which keeps it short of a 5.

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 guidance on when to use this tool versus create_biome, delete_biome, or list_biomes, and no prerequisites are stated. The agent must infer that an existing biome ID is required and that this is the mutation path for name/description changes.

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