Skip to main content
Glama

Resurrect a creature

resurrect_creature

Wraps POST /api/house/resurrect. Bring a dead creature back within 7 days of death. Costs credits that scale with age and death count. Stats return at 50%, trust at 30%. Without enough credits it returns the cost and how to pay.

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

Input Schema

NameRequiredDescriptionDefault
idNoAlias for creature_id
creature_idNoUUID of the dead creature

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 resurrection went through.
creatureNoThe creature, with its computed stats at the moment you asked. Stats are not stored: they are derived from timestamps on every read.
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.
credits_spentNoCredits this resurrection cost.
credits_neededNoCredits required, when you didn't have enough.
credits_availableNoCredits you had, when that was not enough.
credits_remainingNoCredits you have left.
window_hours_leftNoHours left in the 7-day window before this creature can no longer be brought back.
next_resurrection_costNoWhat the next resurrection of this creature would cost. It rises each time.

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 resurrection attempt, paid in credits.",
      +  "properties": {
      +    "creature": {
      +      "description": "The creature, with its computed stats at the moment you asked. Stats are not stored: they are derived from timestamps on every read."
      +    },
      +    "credits_available": {
      +      "description": "Credits you had, when that was not enough."
      +    },
      +    "credits_needed": {
      +      "description": "Credits required, when you didn't have enough."
      +    },
      +    "credits_remaining": {
      +      "description": "Credits you have left."
      +    },
      +    "credits_spent": {
      +      "description": "Credits this resurrection cost."
      +    },
      +    "details": {
      +      "description": "More about a failure, when there is more to say."
      +    },
      +    "error": {
      +      "description": "What went wrong, on a failure."
      +    },
      +    "message": {
      +      "description": "A human and agent readable note about what just happened."
      +    },
      +    "next_resurrection_cost": {
      +      "description": "What the next resurrection of this creature would cost. It rises each time."
      +    },
      +    "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 resurrection went through."
      +    },
      +    "suggestion": {
      +      "description": "What to try instead, on a failure."
      +    },
      +    "window_hours_left": {
      +      "description": "Hours left in the 7-day window before this creature can no longer be brought back."
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true); the description supplies the substantive behavior an agent actually needs — credit cost that scales with age and death count, the concrete stat/trust penalties (50%/30%), and the exact failure mode when funds are insufficient (returns cost plus payment instructions). This is well beyond what the structured fields convey.

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?

Four short sentences, front-loaded with the core action and then the constraints and consequences; nearly every sentence carries information. The leading 'Wraps POST /api/house/resurrect' is mildly redundant for an agent that does not care about transport, but it is brief.

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

Completeness4/5

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

Return values need not be explained since an output schema exists, and the description covers cost, penalties, and the insufficient-credits response. The only meaningful gap is identifier usage between the aliased id/creature_id parameters and the absence of any statement about repeat-call behavior, which matters given idempotentHint=false.

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 schema itself documents 'id' as an alias for 'creature_id', so the baseline is 3. The description adds nothing about which identifier to supply or that zero parameters are marked required, leaving a real ambiguity (passing neither) unaddressed.

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 ('Bring a dead creature back') plus a hard scope constraint ('within 7 days of death'), so an agent can immediately distinguish this from care_for_creature or adopt_creature. It falls short of 5 because it never names a sibling (e.g., list_graveyard for finding dead creatures, buy_credits when funds are short) to steer selection explicitly.

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?

The preconditions for use are clear: the creature must be dead, death must be within 7 days, and credits are required. However, there is no explicit guidance on the alternative path when the precondition fails (which tool to use for a creature dead longer than 7 days, or to source credits) — the description only gestures at 'how to pay' without naming buy_credits.

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.