Skip to main content
Glama

Doxtract

Get inbox

get_inbox
Read-onlyIdempotent

Read one inbox: its name, icon, status, document count, email address, and its fields as a JSON schema (schema, null for a draft with no fields yet). The fields show what kind of document the inbox reads, so use them to decide which inbox a document belongs in.

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

Input Schema

NameRequiredDescriptionDefault
inbox_idYesThe inbox id returned by create_inbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine value beyond them by disclosing the shape of the return (a JSON schema of fields) and an edge case: schema is null for a draft inbox with no fields yet — important behavior an agent would otherwise misread as an error.

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?

Two sentences, front-loaded with the verb and resource before the list of returned attributes. The field enumeration is slightly list-heavy but each item earns its place by documenting a return value that has no output schema behind it.

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?

There is no output schema, so the description must carry return-value semantics, and it does so thoroughly while also explaining the null-schema draft case. The main remaining gap is unspecified behavior for a nonexistent or invalid inbox_id, which an agent would want before calling.

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?

With 100% schema description coverage on the single inbox_id parameter (already documented as "the inbox id returned by create_inbox"), the schema carries the parameter burden. The description adds no syntax, format, or failure-mode detail about inbox_id, so the baseline 3 is appropriate.

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?

"Read one inbox" gives a specific verb and resource, and the enumeration of returned attributes (name, icon, status, document count, email address, schema) tells the agent exactly what this call produces. The singular "one inbox" implicitly contrasts with list_inboxes, but no sibling is named explicitly.

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?

The final clause gives a concrete downstream use case — inspect the fields to decide which inbox a document belongs in — which implies when this tool matters. However, it never states when to call this versus list_inboxes, get_inbox_email, or get_schema, and offers no exclusions or prerequisites.

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.