Skip to main content
Glama

list_organisms

Retrieve and filter individual organisms such as morphs, castes, sexual dimorphisms, and life-history stages by species, biome, theme, or embedding status.

Instructions

List individual organisms (morphs, castes, sexual dimorphisms, life-history stages) with filtering by species, biome, themes, and embedding status.

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_organisms"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch query matching organism name or description
limitNoPagination limit (default: 50)
themeNoFilter organisms containing a specific ecological/phenotypic theme tag
offsetNoPagination offset (default: 0)
biome_idNoFilter organisms by Biome ID
embeddedNoFilter by embedding presence (true for embedded only, false for missing)
species_idNoFilter organisms by Species ID
include_embeddingNoInclude raw 1024-float vector embedding

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden. "List" signals a read, but nothing is said about result shape, ordering, whether pagination is required for large sets, or the cost of include_embedding (raw 1024-float vectors), which is a meaningful payload hazard an agent cannot infer from prose alone.

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 names the resource first and then the filter axes, with zero filler. Nothing could be removed without losing information.

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?

Eight optional parameters with full schema documentation make the tool callable, but with no annotations and no output schema the description should compensate by saying what a result row contains and how pagination behaves. It is adequate to invoke but leaves the return contract entirely undefined.

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 every parameter including q, theme, embedded, and include_embedding is already documented in the schema. The description echoes the four main filter dimensions but adds no syntax, matching semantics, or interaction detail beyond what the schema provides, so the baseline of 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?

States a concrete verb and resource ("List individual organisms") and clarifies scope with a parenthetical covering morphs, castes, sexual dimorphisms, and life-history stages, which usefully separates it from list_species. It does not explicitly name a sibling to route against, so it stops short of a 5.

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?

Filtering context is implied by the enumerated filter axes (species, biome, theme, embedding status), which hints at when the tool is appropriate. However, there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as list_species or the get_* tools for single-record retrieval.

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