Skip to main content
Glama

Doxtract

Create inbox from a schema

create_inbox_from_schema

Create an active inbox from a schema you send, in the same format as a saved layout. The inbox gets its own fields, its email address is returned, and mail and uploads are parsed at once. This path is for the API and MCP only; the console does not offer it.

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>",
      "schema": "<schema>"
    },
    "name": "create_inbox_from_schema"
  }
}

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.
schemaYesA layout is {"type":"object","properties":{...}}. Each property is {"type":T} where T is one of any, null, boolean, string, number, date, array, object. An optional description, at most 400 characters, tells the model how to read that key. An optional required array lists the keys that must be present. A date is a string yyyy-mm-dd. An array adds "items" (one node). An object adds "properties" and may add "required". At most 4 levels below the root, 100 keys, and 16384 bytes.

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?

Beyond the annotations, it discloses that the resulting inbox is active, that it gets its own fields, that the email address is returned in the response, and that mail and uploads are parsed immediately. It does not cover failure behavior such as the uniqueness collision on name (annotations mark it non-idempotent), which leaves one meaningful gap.

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?

Three tight sentences, front-loaded with the core action and followed by effect and channel constraint. The console-availability sentence is lower value but small and genuinely useful routing information, so little is wasted.

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 non-idempotent creation tool with no output schema, the description covers what is produced (an active inbox with fields and a returned email address) and when the channel applies. The nested schema argument is fully specified in the input schema, so no major gap remains apart from duplicate-name handling.

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% and the schema node description already specifies node types, nesting limits, and byte caps in detail. The description's only addition is the cross-reference that the payload matches the saved-layout format, which helps but is modest against an already thorough 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?

"Create an active inbox from a schema you send" is a specific verb plus resource with the distinguishing detail that the schema comes from the caller rather than an existing saved layout. That implicitly separates it from create_inbox, though no sibling is named outright, so an agent must infer the create_inbox vs. create_inbox_from_schema split.

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 description gives channel guidance ("API and MCP only; the console does not offer it") and implies the schema-inline use case, but never explicitly says when to prefer create_inbox with an existing layout over this tool. Usage is only inferable from the phrasing.

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.