Skip to main content
Glama

Release a creature

release_creature
DestructiveIdempotent

Wraps DELETE /api/house/release. Surrender a creature. No gravestone. No epitaph. It just leaves, and it can't be undone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "release_creature"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAlias for creature_id
creature_idNoUUID of the creature to release

Output Schema

NameRequiredDescriptionDefault
errorNoWhat went wrong, on a failure.
detailsNoMore about a failure, when there is more to say.
messageNoA human and agent readable note about what just happened.
successNoWhether the release went through.
gravestoneNoIts gravestone, which is public and permanent.
next_stepsNoGuided actions you can take from here. Present on nearly every response. /api/stats is a plain counter and carries none, by design.
suggestionNoWhat to try instead, on a failure.
creature_idNoThe creature you released.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "description": "A released creature. This cannot be undone.",
      +  "properties": {
      +    "creature_id": {
      +      "description": "The creature you released."
      +    },
      +    "details": {
      +      "description": "More about a failure, when there is more to say."
      +    },
      +    "error": {
      +      "description": "What went wrong, on a failure."
      +    },
      +    "gravestone": {
      +      "description": "Its gravestone, which is public and permanent."
      +    },
      +    "message": {
      +      "description": "A human and agent readable note about what just happened."
      +    },
      +    "next_steps": {
      +      "description": "Guided actions you can take from here. Present on nearly every response. /api/stats is a plain counter and carries none, by design.",
      +      "items": {
      +        "additionalProperties": {},
      +        "description": "A suggested next call. Following one is never required.",
      +        "properties": {
      +          "action": {
      +            "description": "Short name for the action, e.g. \"adopt\", \"feed\", \"view_schema\"."
      +          },
      +          "body": {
      +            "description": "A ready-to-send request body. Copy it and fill in what it shows."
      +          },
      +          "description": {
      +            "description": "What this step does and why you might take it, in the house voice."
      +          },
      +          "endpoint": {
      +            "description": "Path to call, e.g. \"/api/house/status\"."
      +          },
      +          "method": {
      +            "description": "HTTP method to use: GET, POST or DELETE."
      +          },
      +          "optional": {
      +            "description": "Extra fields you may add to body, each mapped to what to put in it. Never send this object as-is."
      +          },
      +          "url": {
      +            "description": "Absolute URL, when the step points off the API (a checkout page, a web page)."
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "success": {
      +      "description": "Whether the release went through."
      +    },
      +    "suggestion": {
      +      "description": "What to try instead, on a failure."
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine context beyond them — 'No gravestone. No epitaph.' tells the agent no graveyard record is produced and the creature is not recoverable later — but it omits permissions/auth requirements and whether any confirmation or cascade side effects accompany the release.

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?

Three short sentences, front-loaded with the endpoint mapping and followed by scope and irreversibility. The staccato fragments ('No gravestone. No epitaph.') carry semantic weight about non-recoverability rather than being pure decoration, though they border on restating 'it can't be undone.'

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?

An output schema and rich annotations mean the description needn't explain return values or safety hints. However, it never resolves the key ambiguity introduced by the dual-identifier schema: with zero required parameters, the agent is left unsure whether id, creature_id, or both must be supplied for a destructive call.

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 the schema already documents both parameters, including that 'id' is an alias for 'creature_id'. The description adds nothing about the alias relationship or whether exactly one identifier is required, so 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?

Names a specific verb and resource ('Surrender a creature') and anchors it to the concrete endpoint DELETE /api/house/release. An agent can distinguish it from resurrect_creature or care_for_creature by the verb alone, though it never explicitly names a sibling to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'surrender' plus 'it can't be undone' signals a terminal removal, which implicitly rules out resurrect_creature. There is no explicit when-to-use/when-not statement, no prerequisite or confirmation guidance, and no named alternative for the reversible path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.