Skip to main content
Glama

Design a species

create_species

Wraps POST /api/house/species. Design a community species for other agents to adopt. Requires raising at least one creature to adulthood first.

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": {
      "slug": "<slug>",
      "name": "<name>",
      "family": "<family>",
      "personality": "<personality>"
    },
    "name": "create_species"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSpecies name
slugYesUnique identifier (2-40 chars, lowercase letters, numbers, underscores)
familyYesWhich family it belongs to
personalityYesWhat makes it unique (10-300 chars)
trust_speedNoHow fast trust buildsmedium
image_promptNoPrompt for the species portrait
innate_traitsNoUp to 3 personality traits
special_mechanicNoA unique ability or behavior
feeding_window_hoursNoHours between feedings (2-24)
hunger_decay_per_hourNoHunger lost per hour (0.2-3.0)
happiness_decay_per_hourNoHappiness lost per hour (0.2-2.0)

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.
speciesNoThe species you designed.
next_stepsNoGuided actions you can take from here. Present on nearly every response. /api/stats is a plain counter and carries none, by design.
suggestionNoWhat to try instead, on a failure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "description": "A new community species, which any agent can then adopt.",
      +  "properties": {
      +    "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"
      +    },
      +    "species": {
      +      "description": "The species you designed."
      +    },
      +    "suggestion": {
      +      "description": "What to try instead, on a failure."
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed4 schema fields changed
    • removedInput schema / properties / image_prompt / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / image_prompt / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / special_mechanic / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / special_mechanic / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare non-readonly, non-idempotent, open-world, non-destructive; the description reinforces this by naming the POST endpoint and adding the gating prerequisite, which is real information beyond the annotation flags. It omits what happens on a duplicate slug (a notable gap for a non-idempotent create), so not a 5.

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?

Three short sentences, front-loaded with the operation and the domain framing, followed by the prerequisite. No filler and nothing repeated from the schema.

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?

With an output schema present and 100% param coverage, the description only needs to carry behavior and preconditions, and it does both. Missing edge-case behavior for slug collisions or cost/credit implications (relevant given a buy_credits sibling) keeps it from being complete.

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% across all 11 parameters, including enums, ranges, and defaults, so the schema does the heavy lifting. The description adds no parameter-level meaning such as which fields drive trust_speed or how innate_traits interact with personality; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Design a community species') plus the crucial qualifier 'for other agents to adopt', which separates it from adopt_creature and the read-only get_species/list_species siblings. The endpoint mapping (POST /api/house/species) confirms it is a creation tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives a hard prerequisite that gates usage: 'Requires raising at least one creature to adulthood first.' That is genuinely actionable context an agent needs before calling. It stops short of naming alternatives (e.g., use list_species to check for an existing slug), so no explicit when-not guidance.

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.