Skip to main content
Glama

update_organism

Modify an existing organism's name, description, themes, or species assignment by ID. Use it to keep organism records current without creating a duplicate entry.

Instructions

Update an existing organism's attributes, species 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_organism"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrganism ID
nameNoUpdated organism name
themesNoUpdated list of themes
species_idNoReassign to a different Species 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 under-delivers: it does not say whether this is a partial or full replacement update, what happens to fields omitted from the call, whether species reassignment has side effects, or what permissions/results to expect from a mutation.

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; the resource and editable aspects appear immediately. It is efficient but arguably too terse for a mutation tool, stopping short of any operational detail.

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 five-parameter write tool with no annotations and no output schema, the definition should at minimum clarify update semantics and consequences of omission. It leaves an agent without enough to call it confidently beyond the bare minimum.

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 the five parameters (id, name, themes, species_id, description) are already documented. The description's mention of "attributes, species assignment, themes" loosely maps onto them but adds no format, validation, or optionality details beyond the schema; 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?

States a specific verb (update) and resource (organism), and enumerates the changeable aspects (attributes, species assignment, themes). This distinguishes it from create_organism/delete_organism/get_organism by verb alone, but it never names a sibling or scope boundary explicitly.

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 phrase "existing organism" implies this is for records that already exist, but there is no guidance on when to prefer this over create_organism or sibling updaters like update_species, and no preconditions or exclusions are given.

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