Skip to main content
Glama

Play a legal action

act

Play the n-th legal action from the last table_state (1-based). Returns the table after the other seat has answered, or the result.

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": {
      "n": "<n>"
    },
    "name": "act"
  }
}

Input Schema

NameRequiredDescriptionDefault
nYeswhich legal action to play: its number in the list the last table_state printed, counted from 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / n / description
      Added value: +"which legal action to play: its number in the list the last table_state printed, counted from 1"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not idempotent, not destructive), and the description adds genuinely non-obvious behavior: invoking it hands the turn to the other seat and returns the updated table or a result. That turn-passing consequence is exactly the kind of effect an agent needs and cannot get from the annotations alone. Remaining gaps are minor (what happens on an out-of-range n).

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 with zero filler; the action selection is front-loaded and the return behavior follows immediately. Every clause carries information.

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 single-parameter, no-output-schema tool, the description covers what it consumes, what side effect it triggers, and what comes back. It leaves 'the result' undefined and says nothing about invalid n or stale table_state, which keeps it from being fully complete.

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?

Schema coverage is 100% and the parameter description already states 'counted from 1' and the tie to the last table_state list, so the description's '(1-based)' and provenance wording largely restate the schema. Baseline 3 applies; no additional syntax, bounds, or error semantics are added.

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 verb ('Play') and resource ('the n-th legal action') with the source of the action list named ('the last table_state'), which implicitly distinguishes it from the sibling that enumerates those actions. It stops short of naming alternatives outright, so an agent infers the table_state → act pairing rather than being told it.

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?

The phrase 'from the last table_state' establishes the precondition and ordering: obtain the action list first, then play an entry from it. There are no explicit exclusions or comparisons to siblings such as 'result', but the required call sequence is clear.

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