Skip to main content
Glama

Take Play Turn

take_turn
Read-onlyIdempotent

Resolve free-text player intent through the parser and mint a session-scoped, read-only turn handle for recording the story outcome without mutating Novel state.

Instructions

Resolve a player intent through the parser and mint a turn handle for the story record. intent is free text parsed by the command resolver; entity_id optionally scopes the parse to the acting entity. The turn is read-only and non-persistent: no Novel state is mutated; the handle is session-scoped, single-use, and consumed by manage_story (action: record), though recording without it still works. Repeated calls mint fresh handles rather than resuming the prior one. Use when: taking a turn before recording its outcome. Do NOT use when: resolving a specific combat round — use manage_combat (action: advance); rolling a ruleset check — use resolve_mechanic (action: roll).

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": {
      "intent": "<intent>"
    },
    "name": "take_turn"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentYesPlayer intent to resolve (take_turn).
entity_idNoActing entity id (take_turn).

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.6/5.0
Behavior4/5

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

Beyond the readOnly/destructive/idempotent annotations, it discloses that the handle is session-scoped, single-use, consumed by manage_story (action: record), and that recording works even without a handle. The statement that repeated calls mint fresh handles rather than resuming is valuable, though it sits in mild tension with idempotentHint=true and could have been reconciled explicitly (same state, different return value).

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 purpose, then parameters, then lifecycle behavior, then use/don't-use routing — a logical order with no filler. Some clauses (e.g., 'though recording without it still works') are dense parentheticals that cost readability, but each carries real information.

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?

With an output schema present and full parameter coverage, the description only needs to cover lifecycle and routing, and it does: handle scope, single-use semantics, downstream consumer, and fallback path. An agent has everything required to call and chain this tool correctly.

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 coverage is 100%, so the baseline is 3; the description earns a step up by explaining that intent is free text interpreted by the command resolver and that entity_id only optionally scopes the parse to the acting entity — meaning the schema's 'Acting entity id' does not convey.

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+resource pair — resolves a player intent through the parser and mints a turn handle — with scope ('no Novel state is mutated') and identifies what the produced artifact is. It is clearly distinguishable from siblings like manage_combat and manage_story, which are named explicitly.

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?

Contains explicit 'Use when: taking a turn before recording its outcome' and 'Do NOT use when' clauses that route two competing needs (combat round resolution, ruleset checks) to the correct sibling tools by name and action. This is the strongest form of the dimension.

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