Skip to main content
Glama

Open Play Session

open_session
Destructive

Start or resume a play session by selecting an optional Novel and badge, then get a recap to continue play after a restart.

Instructions

Open a play session by resuming a Novel, activating a badge, and returning a recap. novel selects the slug and badge the seat; both are optional and fall back to the active Novel and current badge. With no novel and no active Novel, it resumes the only Novel on the server (on a fresh install, the seeded starter), and refuses naming the available slugs when several exist. resume closes the current session window, switches the active Novel, and increments its session count; a badge change persists, is audited, and re-filters tools/list immediately; neither deletes prior Novel state. Session and badge changes are not undoable via manage_history. Use when: starting or resuming a session, especially after a restart. Do NOT use when: creating a Novel — use manage_novel (action: create); running a turn — use take_turn.

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

Input Schema

NameRequiredDescriptionDefault
badgeNoBadge to activate (open_session).
novelNoNovel slug to resume (open_session).

Output Schema

NameRequiredDescriptionDefault
textNoHuman-readable text envelope mirroring the structured result (REQ-001, REQ-548a).
statusYesMachine-readable result status: OK, NEED_INPUT, WARNING, PARTIAL, or an error category (REQ-002, REQ-548c).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the destructive/readOnly/idempotent hints: it discloses that resume closes the current session window, switches the active Novel, increments its session count, that a badge change persists, is audited, and re-filters tools/list immediately, and that neither deletes prior Novel state. It also warns that session and badge changes are not undoable via manage_history, which is exactly the irreversibility context destructiveHint=true implies.

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 action, then side effects, then use/do-not-use routing – a sensible order. It is dense and long for a two-parameter tool, but nearly every clause carries operational value; a slight trim of the fallback enumeration would tighten it.

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

Completeness5/5

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

Covers fallback resolution, failure mode (refusal listing slugs), side effects, audit behavior, and irreversibility. Since an output schema exists, the recap's contents need no explanation, so this is complete for a non-idempotent mutation tool.

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

Parameters5/5

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

Although schema coverage is already 100%, the description adds real meaning: what each parameter selects (slug vs. seat), that both are optional with fallbacks to the active Novel and current badge, and the no-novel/no-active-novel resolution path including the refusal behavior that names available slugs when several exist.

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 and resource ('Open a play session') plus the three effects (resuming a Novel, activating a badge, returning a recap). It distinguishes itself from close_session by describing the inverse operation and explicitly names manage_novel and take_turn as the tools for other jobs.

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

Usage Guidelines5/5

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

Provides explicit 'Use when' (starting/resuming a session, especially after a restart) and 'Do NOT use when' clauses with named alternatives and their action arguments (manage_novel action: create; take_turn). Nothing is left to inference about tool selection.

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