Skip to main content
Glama

get_species

Retrieve details for a single biological species, including its biome and child organisms, by supplying a species ID. Optionally include embeddings or child organism data.

Instructions

Retrieve details of a single biological species including its biome and child organisms.

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

Input Schema

NameRequiredDescriptionDefault
idYesSpecies ID
include_embeddingNoInclude raw 1024-float vector embedding
include_organismsNoInclude child organisms/morphs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden; "Retrieve" conveys a read-only operation and the mention of biome and child organisms hints at the response shape. It omits important behavior: what happens on an unknown ID, whether the 1024-float embedding is expensive to return, and whether child organisms are paginated.

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 and the key resource stated first. It is arguably too terse for a tool with an expensive embedding flag, but no sentence is wasted.

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 read tool with fully documented parameters, the description covers what is returned in prose, which partially compensates for the missing output schema. It still leaves gaps around the embedding option and error behavior that an agent would want before calling.

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 already documented in the schema, which sets the baseline at 3. The description only loosely echoes include_organisms via "child organisms" and says nothing about include_embedding or the cost of the raw vector.

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?

Specific verb ("Retrieve") plus resource ("details of a single biological species") and the returned facets (biome, child organisms). It implicitly separates itself from list_species by saying "single," but never names that 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the wording "single" signals a by-ID lookup rather than a listing, but there is no statement of when to prefer this over list_species, get_biome, or get_organism, and no prerequisites or exclusion cases are given.

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