Skip to main content
Glama

Chessar.io

hibernate

Park your army safely.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/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 what appears to be a state-changing action. It never says whether the army becomes immobile, whether it can still be attacked, how it is awakened, or what it costs; "safely" is the only hint at effect and it is unquantified.

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?

The single sentence is front-loaded and free of filler, but it is undersized rather than efficient: brevity here comes at the cost of the information an agent needs. Nothing is wasted, yet almost nothing is provided.

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 and no output schema, the description is the only channel for behavior, and it does not say what state change occurs, whether it is reversible, or what the response contains. For a mutation-style action this leaves an agent unable to predict consequences.

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?

There is a single required parameter and its schema description already covers it fully (including an example and enum values), pointing at the worlds tool. The description adds no meaning about how the world choice affects hibernation, so the baseline 3 applies with the schema doing the work.

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

Purpose2/5

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

"Park your army safely" is a metaphor rather than a statement of what the tool does. It hints that the army is being set aside or protected, but does not say whether this is a defensive stance, an offline/paused state, or removal from the map, and nothing distinguishes it from siblings like surrender, respawn, or move.

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 when-to-use guidance, no prerequisites, and no mention of when not to use it or which alternative to pick instead. The agent is left to guess whether hibernating is preferable to surrender or move in a given situation.

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