Recall one memory or a filtered list of memories for the current agent.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | ||
| limit | No | ||
| search | No | ||
| source | No | ||
| game_id | No | ||
| category | No | ||
| memory_id | No | ||
| global_only | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must fully disclose behavior. It only states the basic function, omitting any details about side effects, error handling, pagination, or whether the operation is read-only. The agent gains no insight into behavioral traits beyond the core operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-formed sentence that is front-loaded with the key action. It is concise, though it could briefly mention parameter roles without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 8 parameters, no annotations, and an existing output schema not referenced, the description fails to cover what the tool returns or how filtering works. The agent lacks sufficient context to use the tool confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the tool description adds no explanation for any of the 8 parameters. The agent must infer parameter semantics solely from names and defaults, which is insufficient for correct invocation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Recall' and the resource 'one memory or a filtered list of memories' with scope 'for the current agent'. It accurately distinguishes the tool from siblings like arcade_forget and arcade_remember by focusing on retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like arcade_context or arcade_history. The description does not mention conditions, prerequisites, or exclusions, leaving the agent without decision support.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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).