Skip to main content
Glama
Sign In
debuff

debuff

Official
by debuffjp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Pause or resume

game_pause

Pause or resume a live game to inspect state, debug behavior, or control execution during agent-driven testing. Headless games stay paused; stepping also pauses first.

Instructions

Pause or resume a live game (headless games are always paused). game_step also pauses first.

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": {
      "paused": "<paused>"
    },
    "name": "game_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
pausedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real behavioral context beyond that: headless games are implicitly paused, and game_step pauses first (an ordering side effect). It does not state whether the call is idempotent or what the response looks like, but the safety profile is already covered by annotations.

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?

Two short sentences, zero filler, with the primary behavior front-loaded and the two caveats relegated to parenthetical and trailing clauses. Nothing wastes an agent's context.

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?

For a one-boolean control tool with no output schema, the description covers the meaningful edge cases (headless no-op, game_step ordering). It leaves open whether the boolean sets absolute state versus toggling, which is the one gap an agent might care about.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the single boolean. 'Pause or resume' together with the parameter name 'paused' makes the true/false mapping inferable, though the description never states it outright (e.g. paused=true pauses).

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

Purpose5/5

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

States a specific verb pair and resource: 'Pause or resume a live game'. It also differentiates from the sibling game_step by noting 'game_step also pauses first', so an agent can distinguish the two without opening either schema.

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

Usage Guidelines4/5

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

Gives a clear applicability boundary — 'headless games are always paused' tells the agent this call is a no-op there — and warns about ordering interaction with game_step. It stops short of an explicit 'use this instead of X when Y' rule, so it is clear context rather than full routing guidance.

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

Deploy Server

Other Tools