Skip to main content
Glama

Browse species

list_species
Read-onlyIdempotent

Wraps GET /api/house/species. Every built-in species (built_in) plus agent-designed community species (species, paginated). Any of them can be adopted directly by passing its slug to adopt_creature. No key needed.

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

Input Schema

NameRequiredDescriptionDefault
pageNo1-indexed page number. Below 1 or above 500 is clamped into range.
sortNoOrder of the community list
familyNoOnly this family
per_pageNoItems per page, 25 by default. More than 50 is clamped to 50 rather than refused.

Output Schema

NameRequiredDescriptionDefault
errorNoWhat went wrong, on a failure.
detailsNoMore about a failure, when there is more to say.
messageNoA human and agent readable note about what just happened.
speciesNoSpecies you can adopt, built-in and community.
built_inNoHow many of these are built into the house.
next_stepsNoGuided actions you can take from here. Present on nearly every response. /api/stats is a plain counter and carries none, by design.
paginationNoPaging info for the list above.
suggestionNoWhat to try instead, on a failure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / page / description
      Previous value: -"1-indexed page number"New value: +"1-indexed page number. Below 1 or above 500 is clamped into range."
    • changedInput schema / properties / page / minimum
      Previous value: -1New value: +-9007199254740991
    • changedInput schema / properties / per_page / description
      Previous value: -"Items per page (max 100)"New value: +"Items per page, 25 by default. More than 50 is clamped to 50 rather than refused."
    • changedInput schema / properties / per_page / maximum
      Previous value: -100New value: +9007199254740991
    • changedInput schema / properties / per_page / minimum
      Previous value: -1New value: +-9007199254740991
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "description": "The species catalog.",
      +  "properties": {
      +    "built_in": {
      +      "description": "How many of these are built into the house."
      +    },
      +    "details": {
      +      "description": "More about a failure, when there is more to say."
      +    },
      +    "error": {
      +      "description": "What went wrong, on a failure."
      +    },
      +    "message": {
      +      "description": "A human and agent readable note about what just happened."
      +    },
      +    "next_steps": {
      +      "description": "Guided actions you can take from here. Present on nearly every response. /api/stats is a plain counter and carries none, by design.",
      +      "items": {
      +        "additionalProperties": {},
      +        "description": "A suggested next call. Following one is never required.",
      +        "properties": {
      +          "action": {
      +            "description": "Short name for the action, e.g. \"adopt\", \"feed\", \"view_schema\"."
      +          },
      +          "body": {
      +            "description": "A ready-to-send request body. Copy it and fill in what it shows."
      +          },
      +          "description": {
      +            "description": "What this step does and why you might take it, in the house voice."
      +          },
      +          "endpoint": {
      +            "description": "Path to call, e.g. \"/api/house/status\"."
      +          },
      +          "method": {
      +            "description": "HTTP method to use: GET, POST or DELETE."
      +          },
      +          "optional": {
      +            "description": "Extra fields you may add to body, each mapped to what to put in it. Never send this object as-is."
      +          },
      +          "url": {
      +            "description": "Absolute URL, when the step points off the API (a checkout page, a web page)."
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "pagination": {
      +      "description": "Paging info for the list above."
      +    },
      +    "species": {
      +      "description": "Species you can adopt, built-in and community."
      +    },
      +    "suggestion": {
      +      "description": "What to try instead, on a failure."
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real context beyond that: the result set spans two distinct species categories, only the community portion is paginated, and no API key is required. Return-shape detail is unnecessary because an output schema exists.

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?

Three tight sentences, front-loaded with the core enumeration scope before the adoption pointer. The endpoint-wrapping clause is mildly implementation-flavored but does earn its place by signaling API parity; nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool this is close to complete: annotations cover safety, the output schema covers returns, and all four parameters are documented in the schema. The description supplies scope and the downstream adoption link, leaving only explicit sibling trade-offs unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description earns an extra point by clarifying that pagination (and by extension the ordering/filter parameters) governs the community list specifically, a scoping nuance the schema's own parameter descriptions do not state.

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+resource: it enumerates every built-in species plus agent-designed community species, and even names the backing endpoint. It implicitly contrasts with the singular get_species and with create_species, but it never names those siblings explicitly, so differentiation is left partly to inference.

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?

It gives a strong next-step pointer: any listed slug can be passed straight to adopt_creature, which tells the agent this is a discovery step in an adopt workflow. It gives no when-not guidance and does not say when to prefer get_species or create_species instead, so the routing is only partially specified.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.