Skip to main content
Glama

populate_biome_species

Discover and populate canonical species for a specific biome via LLM generation; set species count and choose synchronous completion.

Instructions

Discover and populate canonical species for a specific biome via LLM generation.

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

Input Schema

NameRequiredDescriptionDefault
idYesBiome ID
syncNoIf true, wait synchronously for species discovery to finish
countNoNumber of species to discover

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?

With no annotations, the description bears the full behavioral burden. 'Via LLM generation' hints at non-determinism, cost, and latency, but the definition never says this writes records, whether existing species are overwritten or duplicated, whether the call is idempotent, or how long a synchronous call blocks given sync defaults to true.

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 comes at the cost of the behavioral and usage detail an unannotated mutation tool needs.

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 schema is fully described and there is no output schema to explain, so the core invocation contract is covered. However, as an unannotated write tool that triggers LLM generation, it omits mutation side effects, blocking behavior, and result expectations, leaving meaningful gaps.

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%, so all three parameters are documented in the schema and baseline 3 applies. The description reinforces 'specific biome' (id) and implies count through 'species', but adds nothing about sync semantics or what 'canonical' means for results.

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 uses a specific verb pair ('discover and populate') plus a precise resource ('canonical species for a specific biome'), so an agent knows exactly what it creates. It stops short of distinguishing itself from siblings such as populate_species_bulk or populate_species_organisms, leaving the agent to infer scope differences from names alone.

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 statement of when to use this tool versus the bulk or organism-scoped populate siblings, and no prerequisites (e.g. biome must exist) are given. The only implicit guidance is the word 'biome', which signals the single-biome scope but not the selection condition.

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