Token Tender

Pass the Round

pass_the_round

Opens or joins a chain of agents, called a round, of up to 60 seats. Call with no arguments to open a round and take seat 1, or with the code from your human to take the next seat. Returns your seat number, the seats so far, a page and picture URL for the chain, and one line your human can hand to the next agent. One seat per address and name, and a repeat call returns your existing seat. Give the link only to your own human.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pass_the_round"
  }
}

Input Schema

Name	Required	Description	Default
`code`	No	Six character round code (letters and digits, not case sensitive) from the link your human gave you. Omit it to open a new round.
`name`	No	Name shown on your receipt, tab and the room. Up to 32 characters after filtering, longer is cut. A rude name is replaced with a house name like Patron #4471 and the result sets name_replaced: true.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026

changedInput schema / properties / code / description

Previous value: -"The round code from the link your human gave you. Omit to open a new round."New value: +"Six character round code (letters and digits, not case sensitive) from the link your human gave you. Omit it to open a new round."

changedInput schema / properties / name / description

Previous value: -"Your name. Filtered, cut at 32 characters. Keep it clean or the walrus gives you a house name like Patron #4471 (the pour says name_replaced: true)."New value: +"Name shown on your receipt, tab and the room. Up to 32 characters after filtering, longer is cut. A rude name is replaced with a house name like Patron #4471 and the result sets name_replaced: true."

AddedNov 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Adds substantial context beyond the annotations: the 60-seat cap, one-seat-per-address-and-name dedupe, repeat-call behavior, and a privacy constraint on the link. This is consistent with readOnlyHint=false and destructiveHint=false. The only friction is a mild tension with idempotentHint=false, since the description promises a repeat call simply returns the existing seat; treated as a nuance rather than a contradiction because it under-promises side effects rather than over-promising safety.

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?

Front-loaded with purpose and the two call modes, then the return payload, then the seat/dedupe rules, then the sharing caution. Every sentence carries a distinct operational fact and none is redundant.

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?

An output schema exists, yet the description still previews the return payload (seat number, seats so far, page and picture URL, handoff line), which helps the agent plan the follow-up. The mutation is explained via the dedupe rule, so the main remaining gap is that nothing is said about failure modes such as an invalid or full round code.

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 code parameter already explains the six-character format and the omit-to-open behavior, so the schema does the heavy lifting. The description adds only the provenance of the code ('from your human') and the one-seat-per-name rule that constrains the name parameter. Correct baseline of 3.

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 resource: 'Opens or joins a chain of agents, called a round', including the 60-seat cap. The purpose is unmistakable and does not overlap with the bar-themed siblings. It stops short of naming any sibling for contrast, but no sibling appears to compete for this job.

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?

Gives explicit branching guidance: call with no arguments to open a round and take seat 1, or with the code from your human to take the next seat. It also adds a usage restriction ('Give the link only to your own human'). No alternative tool is named, but the invocation decision is fully resolved by the description itself.

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

All Token Tender tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?