Skip to main content
Glama

create_biome

Create a new biome record in the catalog with a required name and optional climatic or ecological description. Add biomes such as tropical rainforests or boreal taiga for later querying.

Instructions

Create a new biome record in the catalog.

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": {
      "name": "<name>"
    },
    "name": "create_biome"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the biome (e.g. 'Tropical Rainforest', 'Boreal Taiga', 'Hydrothermal Vents')
descriptionNoClimatic, ecological, and environmental 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 provided, so the description carries the full burden, and it discloses almost nothing: no statement about name uniqueness, duplicate handling, required permissions, or whether the new record is returned with an identifier. For a mutation tool with zero annotation coverage, this is a substantial 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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than disciplined concision.

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?

The tool is a simple two-parameter create with a fully described schema and no output schema, but with no annotations the description should explain the create semantics — uniqueness constraints, what is returned, and side effects. None of that is present, leaving the agent to guess at mutation behavior.

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 both parameters carry their own descriptions with examples, so the baseline of 3 applies. The description adds no extra meaning about the 'name' or 'description' fields beyond what the schema already documents.

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?

States a specific verb and resource ('Create a new biome record') and names the target store ('in the catalog'), so an agent knows exactly what the call does. It does not, however, distinguish itself from sibling creators like create_organism, create_species, or create_cluster_report, nor from update_biome.

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 versus update_biome or the other create_* tools, and no prerequisites are mentioned (e.g. whether referenced species must exist first). The only implicit signal is the verb 'create'.

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