Skip to main content
Glama

create_organism

Creates a new individual organism or morph record under an existing parent species, capturing its name, phenotypic traits, and behavioral or caste description for taxonomic modeling.

Instructions

Create a new individual organism/morph record under a parent species.

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": {
      "species_id": "<species_id>",
      "name": "<name>"
    },
    "name": "create_organism"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName or designation of the organism (e.g. 'Adult Male Pride Leader', 'Major Soldier Worker')
themesNoPhenotypic themes and traits (e.g. ['sexual dimorphism', 'territorial defense'])
species_idYesParent Species ID
descriptionNoPhenotypic, behavioral, or caste 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?

No annotations are supplied, so the description carries the full behavioral burden. It never says whether name must be unique within a species, whether an embedding is generated automatically, what identifier is returned, or whether the create is reversible — all material for a mutation tool.

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 with no filler; the verb and scope come first and nothing is repeated. It is exactly as long as the information it actually conveys warrants.

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 create/mutation tool with no annotations and no output schema, the description omits return values, uniqueness rules, and post-creation side effects. The schema documents inputs well, but an agent still cannot predict what comes back or what constraints will cause failure.

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 coverage is 100% and each of the four parameters already has a descriptive string with examples, so the schema does the heavy lifting. The description only reinforces the parent-child relationship via 'under a parent species' and adds no format, uniqueness, or default semantics beyond that.

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?

The description states a specific verb and resource ('Create a new individual organism/morph record') and scopes it 'under a parent species', which distinguishes it from create_species. It stops short of naming the sibling it differs from, but the individual-vs-species distinction is inferable.

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 or when-not guidance: nothing says to use update_organism for existing records, or that a species must already exist. The only hint is the phrase 'under a parent species', which implies the species_id prerequisite but never states it.

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