Skip to main content
Glama

Doxtract

Upload a document to an inbox

upload_document

Add one document to an inbox. It is read with the inbox's fields in the background, the same as a document dropped into the inbox in the console, and costs 1 credit per page. Send the file as file_base64 (a PDF, PNG or JPEG) with its file_name. Returns the new document's id. Upload only to the inbox the document belongs in: call get_inbox to read an inbox's fields when you are not sure.

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>",
      "file_name": "<file_name>",
      "file_base64": "<file_base64>"
    },
    "name": "upload_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
inbox_idYesThe inbox id returned by create_inbox.
file_nameYesThe file's name, such as invoice-1042.pdf. Shown in the inbox.
file_base64YesThe file, base64-encoded: a PDF, PNG or JPEG. The type is read from the bytes, not the name. The size limit is the workspace plan's per-document limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, so the description's added value is real: it discloses asynchronous background processing against inbox fields, a per-page credit charge, accepted file types, and that the new document's id is returned. These are operational facts an agent cannot derive from annotations or schema.

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?

Four short sentences, front-loaded with purpose, then mechanics, then cost, then the routing rule. Each sentence carries distinct information with no repetition of the title or schema.

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 write tool with no output schema, the description covers return value (new document id), processing model, and cost. It stops short of stating what happens on a rejected file or how to observe processing completion, which would matter for a background-read workflow.

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 all three parameters are already documented, including format, size limits, and that the type is sniffed from bytes. The description restates the file_base64/file_name pairing and formats but adds no new semantics, so 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?

States a specific verb and resource ('Add one document to an inbox') and adds the key behavioral detail that it is read with the inbox's fields in the background, which separates it from a plain parse call. It never names a sibling it is not, so the differentiation is implied 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear routing rule: 'Upload only to the inbox the document belongs in: call get_inbox to read an inbox's fields when you are not sure', naming a concrete alternative tool and the condition that selects it. The cost note (1 credit per page) further informs the use decision, though there are no explicit when-not-to-use 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.