Skip to main content
Glama

delete_species

Deletes a species by ID along with its associated individual organisms, removing the species record and linked organism data.

Instructions

Delete a species and its associated individual organisms.

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

Input Schema

NameRequiredDescriptionDefault
idYesSpecies ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden; it does deliver one genuinely important fact — that associated individual organisms are removed as a side effect. However, it says nothing about irreversibility, required permissions, or behavior when the ID does not exist or is already deleted.

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 short sentence with zero filler, front-loading the action and immediately naming the cascading consequence. Nothing is redundant or buried.

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

Completeness3/5

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

For a destructive mutation with no annotations and no output schema, the cascade disclosure is the most valuable piece and it is present. Still missing are permanence/reversibility, permission requirements, and the failure mode for an unknown ID, which an agent needs before calling a delete.

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 the single `id` parameter is documented as "Species ID to delete", so the schema already carries the meaning. The description adds no format, range, or lookup-hint detail beyond it, which is the expected baseline.

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 and resource ("Delete a species") plus a key scope detail — the cascade to associated individual organisms — so the agent knows this is not just a row removal. It does not differentiate from siblings such as delete_organism, but the target resource is unambiguous.

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 guidance on when to use this versus delete_organism or other deletion tools, no stated preconditions, and no warning about when deletion should be avoided. The agent must infer all usage context from the name alone.

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