Skip to main content
Glama

Doxtract

Create inbox

create_inbox

Create an inbox in this workspace and return its id and email address. Send template (a built-in template slug: invoice, receipt, bank_statement, purchase_order) to make it ACTIVE with that template's fields, the same as creating one in the console. Without a template it is a DRAFT that does not parse yet.

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": {
      "name": "<name>"
    },
    "name": "create_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoA Lucide icon name, such as "file-text" or "receipt". Send null to go back to the default. Shown on the inbox card.
nameYesThe inbox name. Unique in the workspace.
templateNoA built-in template slug. Omit it for a draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only say this is a non-destructive, non-idempotent write with no open-world access. The description adds real behavioral context beyond that: the template parameter determines whether the inbox is ACTIVE and parsing or a DRAFT that does not parse, and it names the return values. It says nothing about failure modes such as name uniqueness collisions, which the schema hints at.

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?

Three sentences, front-loaded with the action and return values, then the template/draft distinction. No filler; the console analogy is the only marginally expendable phrase.

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 three-parameter creation tool with no output schema, it covers what is created, what is returned, and how state depends on the template. Gaps are the missing differentiation from create_inbox_from_schema and no mention of duplicate-name behavior.

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 coverage is 100%, so the baseline is 3. The description adds the semantic consequence of `template` (ACTIVE vs DRAFT), but its slug list (invoice, receipt, bank_statement, purchase_order) is only a partial subset of the seven-value enum, which risks under-informing an agent that relies on prose over the schema.

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 ("Create an inbox in this workspace") and adds the useful outcome ("return its id and email address"). It does not, however, distinguish itself from the sibling create_inbox_from_schema, which an agent would reasonably confuse with this tool.

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?

Gives a clear conditional: send a template to get an ACTIVE, parsing inbox; omit it to get a DRAFT that does not parse yet. That is genuine when-to-use guidance for the main decision. It stops short of naming alternatives or exclusions (e.g. when to prefer create_inbox_from_schema).

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.