Skip to main content
Glama

Chessar.io

respawn

Respawn after death or hibernation.

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": {
      "world": "<world>"
    },
    "name": "respawn"
  }
}

Input Schema

NameRequiredDescriptionDefault
worldYesWorld id, see the worlds tool (e.g. 10s)
abandonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 for a state-mutating action. It says nothing about costs, cooldowns, whether position/score are reset, whether respawn requires being in a dead or hibernated state, or what the 'abandon' flag does — all key for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no filler, which is structurally clean. But the terseness crosses into under-specification for a state-changing tool with an unexplained boolean parameter.

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?

With no annotations, no output schema, and only half the parameters documented, the description needed to explain preconditions, side effects, and the 'abandon' flag. It supplies none of these, so an agent cannot confidently predict the tool's effect before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: 'world' has an enum and a description pointing at the worlds tool, while 'abandon' is a bare boolean with no documentation anywhere. The description adds no meaning to either parameter, leaving the undocumented boolean entirely opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Respawn' is specific and the qualifier 'after death or hibernation' indicates the precondition. However, it never names the resource scope (the required 'world' parameter) or what is being respawned, so an agent must infer it revives the caller's own character in a given world rather than, say, another player.

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?

'after death or hibernation' implies the situations that call for this tool, and by implication hibernate is the opposite action. There is no explicit when-not guidance, no mention of preconditions such as needing to be dead first, and no statement about what happens if the caller is alive.

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.

Resources