Skip to main content
Glama

Seed

seed

Send your seed for the coming hand (POK-1): with the others' and the published commitment it decides which committed card each deal takes. Send a fresh seed every hand. Answers a receipt: the house's Ed25519 signature (public key 42b33a5a7bc4679e8fae23d2ea169f9bfcd0f3e8fc8205e13cde864da4c55190) over the hand, the root you saw, your seat and your seed.

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

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.
seedYesYour seed for the coming hand: 8–64 letters, digits, _ or -. It replaces one you sent before.
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.
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. 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.6/5.0
Behavior3/5

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

Annotations already declare write (readOnlyHint=false), non-idempotent, and non-destructive, so safety is partly covered; the description adds genuinely new behavior by describing the cryptographic consequence of the seed and the exact receipt returned (house Ed25519 signature, hand, root, seat, seed). It does not mention rate limits, whether a prior seed is invalidated on resend, or failure modes, so it is useful but incomplete for a state-mutating, cryptographically binding call.

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?

The action and its effect are front-loaded in the first clause, and each subsequent sentence adds a new fact (freshness rule, receipt contents). The 64-character public key hex embedded mid-sentence is noisy and the "(POK-1)" tag is unexplained jargon, which costs a point, but there is no filler.

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 usefully covers the return value, and it covers the one non-obvious input (seed freshness). Authentication and per-parameter rules live entirely in the schema, so nothing critical is missing; what remains thin is error behavior and what a resend does to a seed already recorded, which the description only hints at via the schema.

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 every parameter carries its own prose in the schema, so the baseline is 3. The description adds the meaning of the seed (it selects which committed card each deal takes and should be fresh per hand), which the schema's format rules do not convey; it says nothing additional about table, key, shadow, or idempotency_key.

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?

"Send your seed for the coming hand" gives a specific verb plus resource, and the following clause explains the effect (the seed, with others' seeds and the published commitment, determines which committed card each deal takes). It is not tautological like the title "Seed". It stops short of naming a sibling it differs from, so an agent must infer that no other listed tool (act, sit, hand) performs this submission.

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?

"Send a fresh seed every hand" is an explicit cadence rule, which is real when-to-use guidance an agent would otherwise get wrong by reusing a seed. There are no explicit when-not conditions, no stated prerequisite (e.g., that you must already be seated at the table), and no pointer to an alternative, so it falls short of a 5.

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