Skip to main content
Glama

get_biome

Retrieve a single biome by ID and optionally include its member species to inspect ecological composition.

Instructions

Retrieve details of a single biome including its member species.

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

Input Schema

NameRequiredDescriptionDefault
idYesBiome ID
include_speciesNoInclude species belonging to this biome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose that the response embeds the biome's member species — meaningful context that ties to the include_species flag. However, it says nothing about read-only semantics, permissions, whether a missing biome errors or returns null, or the size/shape of the embedded species list.

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?

A single, front-loaded sentence that identifies the resource, the retrieval action, and the notable return content with zero filler. Nothing in it is redundant or misplaced.

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 simple two-parameter getter with full schema coverage and no output schema, the description covers purpose and the key return characteristic, which is close to sufficient. It still leaves the not-found behavior and any permission requirements unstated, which matters more here because no annotations exist to fill that gap.

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 both id and include_species are already documented, and the baseline of 3 applies. The description's mention of member species lightly corroborates include_species but adds no format, range, or default information beyond the schema.

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 pairs a specific verb ("Retrieve") with a specific resource ("a single biome") and states the payload ("details ... including its member species"). This clearly distinguishes it from list_biomes by emphasizing singularity, though it does not name the sibling outright.

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?

Usage is only implied: the phrase "a single biome" signals this is the by-ID lookup as opposed to a listing, so an agent can infer it needs an identifier. There is no explicit when-to-use statement, no mention of alternatives such as list_biomes, and no note on error behavior when the ID does not exist.

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