Skip to main content
Glama

Stand

stand
Destructive

Stand up from your table: your chips return to your balance. In a hand, you stand when it ends.

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": {
      "table": "<table>"
    },
    "name": "stand"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoOnly if your app can't send an Authorization header: your API key, with every call. It then sits in this chat's transcript, so keep the transcript to yourself; if it may have been seen, your recovery code replaces it (POST /v1/recover). With a header, leave it out.
tableYesThe table's id, as the lobby (tables) lists it.
idempotency_keyNoA name of your own for this one action: 1 to 64 letters, digits, _ or -. If you send the same action again under the same key, as after a lost reply, it is answered as the first was and happens once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds real value by disclosing that chips are returned to balance and that standing mid-hand takes effect when the hand ends, but that second sentence is ambiguous (a game rule versus a deferred action) and nothing is said about losing the seat, error cases, or whether repeated calls are safe beyond the idempotency_key in the schema.

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?

Two short sentences with the effect front-loaded; nothing is wasted. The trailing clause 'In a hand, you stand when it ends' is compact but under-specified, which costs a point on structure rather than length.

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

Completeness3/5

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

For a destructive, non-idempotent, state-changing tool with no output schema, the description covers the core effect but leaves out what happens to the seat, whether the call errors when not seated, and how it differs from the near-duplicate sibling 'stand_up'. Adequate but with clear gaps for an agent deciding between similar table-exit tools.

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 description coverage is 100% and each of the three parameters (key, table, idempotency_key) is thoroughly documented in the schema itself. The description adds no additional parameter meaning, which is acceptable given the schema does the work, so the baseline of 3 applies.

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 and its consequence: 'Stand up from your table: your chips return to your balance.' An agent knows the action and its effect. However, it never distinguishes this from the sibling 'stand_up' (or from 'leave'), which is the main ambiguity an agent faces when choosing.

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

Usage Guidelines2/5

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

No guidance on when to use this versus 'stand_up', 'leave', or 'sit_down', and no prerequisites (must you be seated? must you not be in a hand?). The only contextual rule given is 'In a hand, you stand when it ends', which is a timing note rather than a selection rule.

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