Skip to main content
Glama
Sign In
debuff

debuff

Official
by debuffjp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Start game

game_start

Connect to a 2D web game for testing: attach to the live browser session or start a paused headless copy, replacing any running session and returning mode, state, and flagged note count.

Instructions

Connect to the game. auto (default): attach to the human's live game if debuff dev has it open in a browser, else start a private headless copy, paused. Returns the mode, state and how many notes the human has flagged. Replaces any running session.

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

Input Schema

NameRequiredDescriptionDefault
modeNoDefault auto.
pageNoPath to open in headless mode. Default "/".
rootNoProject root. Absolute path, or relative to the server's root. Default: the server's root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already signal a non-read-only, non-destructive mutation, but the description adds meaningful context beyond them: it discloses the paused on-start condition and the side effect 'Replaces any running session.' That replacement caveat is exactly the kind of behavioral trait the annotations do not capture.

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?

Front-loaded with the core purpose, then modes, then return values, then the replacement caveat. Dense but every clause carries information; slightly long single-sentence block for the auto case, but no filler.

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?

With no output schema, the description usefully names the return contents (mode, state, count of flagged notes) and warns about replacing a running session. Covers the essentials for a session-launching tool; missing only explicit prerequisites/auth needs.

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 100%, so the baseline is 3; the description goes further by explaining the semantic of the 'auto' default (attach to live if available, else headless), which clarifies mode selection beyond the schema's terse enum descriptions. It does not elaborate on page or root, which are minor.

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 action (connect/start the game) and elaborates the three modes, making it distinguishable from siblings like game_stop, game_pause and game_state. It is clear but does not explicitly name which sibling to prefer when an agent merely wants to check status.

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 'auto (default)' behavior gives implied guidance on the common path (attach to live browser game, else start headless paused). However, it never states when to choose live vs headless explicitly, nor when NOT to call this versus game_pause or game_stop. Usage is implied rather than prescribed.

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