Skip to main content
Glama

Doxtract

Get inbox email address

get_inbox_email
Read-onlyIdempotent

Read an inbox's email address and whether it accepts mail. The address is created the first time it is read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inbox_id": "<inbox_id>"
    },
    "name": "get_inbox_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
inbox_idYesThe inbox id returned by create_inbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context that annotations cannot convey: reading is not purely passive because the address is provisioned on first read, which matters for any agent reasoning about side effects. It does not detail failure modes or what 'does not accept mail' implies operationally.

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?

Two short sentences, zero filler, with the primary capability stated first and the lazily-created side effect second. Nothing could be removed without losing information.

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?

With no output schema, the description does the needed work by naming both returned values (the address and whether it accepts mail). Combined with 100% schema coverage and full annotation coverage, this is nearly complete; only error or empty-state behavior is left unstated.

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 100%, with inbox_id documented as the id returned by create_inbox, so the schema carries the meaning. The description adds nothing about the identifier beyond what the schema states; baseline 3 applies.

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 description gives a specific verb and resource ("Read an inbox's email address") plus the secondary field (mail acceptance), which distinguishes it from a general get_inbox. It stops short of naming a sibling or stating scope boundaries, so differentiation is inferable rather than explicit.

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?

Usage is only implied: an agent learns this is the way to obtain an address, and that it must be read before the address exists. There is no explicit when-to-use versus get_inbox, list_inboxes, or the set_inbox_email_enabled toggle, and no stated preconditions or exclusions.

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.