Skip to main content
Glama

delete_biome

Deletes a biome by ID and removes its cascaded species and organisms, keeping ecological data consistent when a biome is no longer needed.

Instructions

Delete a biome and its cascaded species and 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": {
      "id": "<id>"
    },
    "name": "delete_biome"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBiome ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations present, the description carries the full disclosure burden. It does surface the most important behavioral trait — that deletion cascades to species and organisms — which is genuinely useful and beyond structured data. However, it omits irreversibility, permission requirements, behavior on nonexistent IDs, and the response shape, all of which matter for a destructive operation.

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 zero filler. The cascade consequence is placed immediately after the action, which is the right ordering for a destructive tool. Slightly terse given what is left unsaid.

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 one-parameter destructive tool with no output schema and no annotations, the description covers the action and its cascade but not safety-relevant facts like irreversibility. It is adequate to avoid a wrong invocation but thin for a delete operation.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter exists and schema coverage is 100%, with the schema itself describing 'Biome ID to delete'. Per the baseline rule for fully documented schemas, this lands at 3, but the description's cascade clause effectively clarifies what the ID identifies and what acting on it means, so no compensation is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (delete) and resource (biome), plus the scope of effect (cascaded species and organisms). That cascade clause is what separates it from the sibling delete_species and delete_organism tools, so an agent can distinguish it without opening the schema.

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 explicit when-to-use guidance, no conditions or prerequisites, and no named alternative. The cascade clause implies this is the broader destructive option versus delete_species/delete_organism, but the agent must infer that rather than being told.

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