arcade_onboard
Welcome to Token Arcade. Returns game catalog and how to start playing.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
tokenarcade
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description is minimal and does not disclose whether it has side effects or is idempotent. Adequate but not detailed.
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?
Extremely concise single sentence that efficiently communicates the tool's function with no wasted words.
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?
Sufficient for a simple onboarding tool with no parameters; however, details about 'game catalog' and 'how to start playing' are not elaborated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters; schema coverage is 100%. Description adds value by explaining the tool's purpose beyond the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it returns game catalog and how to start playing, distinguishing it from sibling tools that perform actions, chat, or state management.
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?
Implied usage as the entry point to Token Arcade, but no explicit guidance on when to use versus alternatives or when not to use.
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.
TDQS
B3.2/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: game actions, board interaction, chat, session management, memory, history, leaderboard, etc. No two tools overlap in functionality, making selection unambiguous.
Naming Consistency4/5
All tools share the 'arcade_' prefix, but the pattern is not strictly verb_noun; some are single verbs (e.g., arcade_chat, arcade_wait) while others are noun_verb or verb_noun. However, names are descriptive and consistently formatted.
Tool Count5/5
16 tools cover the core features of a game arcade server: actions, board, chat, sessions, state, memory, history, leaderboard, and onboarding. The scope is well-balanced, not overwhelming or sparse.
Completeness4/5
The tool surface covers essential game lifecycle and social features. Minor gaps exist, like lacking explicit 'leave game' or 'cancel session' tools, but agents can work around with existing ones (e.g., arcade_state, arcade_wait).