Skip to main content
Glama

update_species

Update an existing species' attributes, biome assignment, or themes by ID to keep ecological records accurate.

Instructions

Update an existing species's attributes, biome assignment, or themes.

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": "update_species"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSpecies ID
nameNoUpdated species name
themesNoUpdated list of themes
biome_idNoReassign to a different Biome ID
descriptionNoUpdated 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, and it says nothing about partial-update semantics (are omitted fields left untouched or cleared?), failure behavior for a nonexistent id, permissions, or reversibility. For a mutation tool with zero annotation coverage this is a substantial gap beyond the single word "Update".

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 or redundancy. It is efficient, though its brevity is part of why behavioral detail is absent.

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?

The input schema is fully documented and there is no output schema to explain, but for a 5-parameter mutation tool with no annotations the description should clarify partial-update behavior and what happens when the id is not found. Those omissions are material for correct invocation.

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% and every field (id, name, themes, biome_id, description) is documented in the schema itself. The description's phrase "attributes, biome assignment, or themes" loosely maps onto those fields but adds no format, constraint, or optionality detail beyond the schema, so the baseline 3 applies.

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?

"Update an existing species's attributes, biome assignment, or themes" gives a specific verb (update) plus resource (species) and enumerates the mutable facets, which lets an agent distinguish it from create_species, delete_species, and get_species. It does not, however, explicitly contrast itself with the other update_* siblings (update_biome, update_organism), so the differentiation rests on the resource noun alone.

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?

The word "existing" implies the target must already exist, which is the only usage signal. There is no guidance on when to prefer this over upsert_species_batch or populate_species_bulk, no statement of prerequisites (does the species need to exist or will it error?), and no exclusions.

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