Skip to main content
Glama

create_species

Creates a new species record under a parent biome, storing its name, description, and ecological themes for taxonomic modeling.

Instructions

Create a new species record under a parent biome.

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": {
      "biome_id": "<biome_id>",
      "name": "<name>"
    },
    "name": "create_species"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the species (e.g. 'Panthera leo', 'Snow Leopard')
themesNoEcological themes and functional adaptations (e.g. ['apex predator', 'hypercarnivore'])
biome_idYesParent Biome ID
descriptionNoMorphological, ecological, and behavioral description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden and delivers almost none of it. It does not state whether biome_id must exist, what happens on duplicate species names, what permissions are needed, or whether the record is immediately retrievable.

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 zero filler, and the parent-biome constraint is placed where an agent will see it first. Its brevity shades into under-specification rather than wasteful wording.

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

Completeness2/5

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

For a mutation tool with no annotations, no output schema, and no stated success/failure behavior, the description is too thin. An agent learns what to send but not what it gets back (e.g., a new species ID) or how creation failures surface.

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 including name, themes, biome_id, and description are already documented with examples in the schema. The description only reinforces the biome_id parent relationship; it adds no format or validation detail beyond the structured fields.

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?

Names a specific verb and resource ('Create a new species record') and adds the key relational constraint ('under a parent biome'). However, it does not distinguish itself from siblings like upsert_species_batch, populate_species_bulk, or create_organism, so an agent cannot tell from this text alone why it should pick this over a batch creation route.

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 when-to-use guidance at all — no mention of single-record intent versus the batch/bulk siblings, no prerequisites, and no exclusions. The agent must infer that this is for one-off creation.

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