Skip to main content
Glama

Hand

hand
Read-onlyIdempotent

A finished hand's proof: the commitment, the seeds, all 52 leaves, and the openings of the board, your own cards and the showdown's. Folded hands are never revealed. Check it with verifyDeal in https://artis.bar/rules/deal.js, and the root against the receipt the house signed (public key 42b33a5a7bc4679e8fae23d2ea169f9bfcd0f3e8fc8205e13cde864da4c55190).

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>",
      "hand": "<hand>"
    },
    "name": "hand"
  }
}

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.
handYesThe hand's id, as the table showed it.
tableYesThe table's id, as the lobby (tables) lists it.
shadowNoOnly without an API key: the pass that arrive answered as `shadow`. Send it with every action after arriving, from wherever you call, and keep it to yourself. With a key, leave it out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / shadow
      Added value: +{
      +  "description": "Only without an API key: the pass that arrive answered as `shadow`. Send it with every action after arriving, from wherever you call, and keep it to yourself. With a key, leave it out.",
      +  "pattern": "^[A-Za-z0-9_-]{32}$",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior on top: the exact contents of the returned bundle, the disclosure rule that folded hands are never revealed, and a concrete verification route with the house's signing public key. That materially changes how an agent should handle and trust the output. It is not a 5 because pagination, size, and the failure mode for folded hands remain unstated.

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 sentences, no filler, with the payload scope front-loaded before the verification instructions. The opening fragment ('A finished hand's proof:') is a deliberate summary rather than wasted words. Slight deduction only because the public key hash is a long opaque token that could have been referenced more cheaply.

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 carries the full burden of describing the return value — and it does, enumerating the commitment, seeds, leaves, and the specific opening sets. It also supplies the off-tool verification procedure and the disclosure constraint on folded hands. The remaining gap is the behavior on unfinished/folded hands (error versus restricted bundle), which an agent would want before calling.

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 schema descriptions are unusually rich — including when to omit `key` or `shadow` and the transcript-exposure warning — so the schema already does the heavy lifting. The description contributes nothing about `table`, `hand`, `key`, or `shadow` beyond that. Baseline 3 is the correct ceiling here.

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?

The description names a specific resource — the proof bundle for a finished hand — and enumerates its parts (commitment, seeds, 52 leaves, openings). That is far more precise than a bare 'Hand'. It stops short of a 5 because the verb is implicit (it reads as a noun phrase describing a payload) and no sibling is named, so the agent must infer that this is a read of a completed hand versus `board`, `history`, or `table`.

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?

Usage is only implied: fetch this to obtain a verifiable proof of a completed hand, then check it with `verifyDeal`. The 'Folded hands are never revealed' clause hints at a precondition, but it never states what happens if the hand is unfinished or folded — error, partial payload, or empty — nor does it point at an alternative tool for live state. The verification path is explained, but the when-to-call guidance is left to inference.

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