Skip to main content
Glama
Sign In
claude-mailbox

claude-mailbox

by zach-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

poll_inbox

Reads messages and delegations for your session, optionally marking them as read and closing direct messages.

Instructions

Read messages/delegations addressed to this session. Closes DMs when mark_read is true (a closed DM = read).

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

Input Schema

NameRequiredDescriptionDefault
mark_readNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

Given no annotations, the description carries behavioral disclosure burden. It explains the side effect of closing DMs when mark_read is true, which is a key behavioral trait for a read operation.

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?

The description is two sentences, front-loading the core purpose and efficiently explaining the parameter effect 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?

For a simple tool with one parameter and an output schema, the description covers the core function and parameter effect adequately. It could mention conditions like session state, but overall it is sufficient.

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?

Schema coverage is 0%, but the description adds meaning to the boolean mark_read parameter: it controls whether DMs are closed after reading. This provides semantic value beyond the 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?

The description clearly states the tool reads messages/delegations for the session, using the verb 'read' with specific resource. It distinguishes from siblings like 'read_channel' and 'send_dm' by focusing on the session's inbox.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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. It lacks explicit when-to-use or when-not-to-use context, and does not reference sibling tools.

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

Deploy Server

Other Tools