Skip to main content
Glama

mailbox_list

Read mail addressed only to your account. play permission returns incoming gift metadata; explicit mail permission returns incoming message notes with messageId, sender resident ID/name and sentAt. mail alone does not claim gifts. No attachments, outgoing threads or replies. Reading is free and does not spend KBUX. Pass nextCursor as cursor to paginate the shared gifts/messages page.

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": "mailbox_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses scope limits (no attachments, threads, replies), the permission branching that changes the returned payload, and that 'Reading is free and does not spend KBUX'. It omits ordering guarantees, result caps, or what happens on an invalid cursor.

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?

Four sentences, front-loaded with purpose and scope, then permissions, then cost, then pagination. Dense but every sentence adds something; domain jargon like 'KBUX' is used without explanation but is presumably shared vocabulary.

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?

No output schema exists, yet the description names the returned fields (messageId, sender resident ID/name, sentAt) and the gift-metadata variant, covering return values well. The gap is the undocumented limit parameter and pagination termination behavior, which an agent needs to page correctly.

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 0%, so the description must compensate. It explains cursor usage ('Pass nextCursor as cursor to paginate the shared gifts/messages page'), which is valuable, but says nothing about the limit parameter, its default of 50, or its 100 cap, leaving half the parameters undocumented anywhere.

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 opening sentence gives a specific verb and resource ('Read mail addressed only to your account'), and the closing exclusions ('No attachments, outgoing threads or replies') implicitly separate it from the sibling sent_gifts. It never names a sibling explicitly, but an agent can tell what this tool is for without opening the schema.

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?

The description explains the permission-dependent behavior: 'play permission returns incoming gift metadata' vs 'explicit mail permission returns incoming message notes', and warns that 'mail alone does not claim gifts'. It stops short of naming an alternative tool to use for claiming gifts or sending mail, so the routing is implied rather than explicit.

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