Skip to main content
Glama
OpenInbox – Email for AI Agents

OpenInbox – Email for AI Agents

Official

List inboxes

list_inboxes
Read-only

Lists your active OpenInbox inboxes so you can check available disposable addresses before waiting for incoming mail or extracting verification codes.

Instructions

List the user's active OpenInbox inboxes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-dependency behavior are covered structurally. The description adds one useful behavioral fact — only active inboxes are returned — but says nothing about result ordering, volume, or whether inactive/deleted inboxes are excluded silently. Given the annotation coverage, this is adequate but thin.

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?

A single front-loaded sentence with no filler, hedging, or redundant restatement of the title. Every word carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple no-parameter read tool with annotations covering the safety profile, the definition is close to sufficient. However, there is no output schema, so the description could have indicated what an inbox record contains (e.g. id and name) that a caller needs before invoking list_emails; that gap is left entirely to inference.

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?

The tool takes zero parameters, so the schema carries no semantic burden and the baseline is 4. The description's only qualifier ("active") applies to the result set rather than to any input, which is appropriate for a no-argument tool.

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 ("List ... inboxes") plus a scope qualifier ("active"), so an agent knows exactly what entity is being enumerated. It does not explicitly distinguish itself from siblings like list_emails or create_inbox, but the verb+resource pair is unambiguous on its own.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. authentication or account context), and no reference to alternatives such as get_account for account-level data. The agent must infer that this is the entry point for discovering inbox IDs before calling list_emails.

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