Skip to main content
Glama

list_biomes

Retrieve registered biomes with species counts, filtering by name or description and paginating results; optionally include associated species.

Instructions

List biomes (global ecosystems, climatic zones, and primary environmental regimes) registered in Biologist with species counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_biomes"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFilter biomes by name or description substring
limitNoPagination limit (default: 50)
offsetNoPagination offset (default: 0)
include_speciesNoInclude species associated with each biome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it only states the return content. It does not state that the operation is a safe read, does not mention pagination/ordering behavior beyond what the schema encodes, and leaves ambiguous whether species counts appear only when include_species is true or are always computed (a potentially expensive operation).

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 with zero filler; the parenthetical definition of biome adds genuine disambiguation rather than padding. Nothing could be trimmed without losing meaning.

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 zero-required-parameter read tool with a fully documented schema and no output schema, the description covers purpose and return shape adequately. It falls short on routing guidance and on the cost/semantics of the species-count aggregation, which is the main thing an agent would need to decide between this and get_biome.

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 four parameters (q, limit, offset, include_species) are already well documented with types, defaults, and bounds. The description adds no parameter-level meaning and even creates mild ambiguity about the relationship between 'with species counts' and the include_species flag, so 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 gives a specific verb and resource ('List biomes'), defines what a biome is ('global ecosystems, climatic zones, and primary environmental regimes'), and states the payload includes species counts. It is clearly distinct from get_biome (singular) and populate_biomes (a write), though it never names a sibling explicitly.

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 get_biome for a single record or populate_biomes/upsert_biomes_batch for writes. Usage is only implied by the verb 'List', and no prerequisites or exclusions are stated.

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