Skip to main content
Glama

upload_intake

Upload ANY file; the system decides what it is (the unified intake queue, the web app's Documents > Upload). file_base64: raw bytes, base64.

Prefer this unless plainly an invoice; always for bank statements (CAMT.053 XML, PDF, CSV or .xlsx; not legacy .xls), matched to the registered bank account by IBAN; journal/accounting exports; balance sheets, P&L and VAT filings. A mixed .zip is routed per file.

Returns 202 and the queue row; poll get_intake for the outcome and targets. An unroutable file fails with its reason, never dropped.

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": {
      "company_id": "<company_id>",
      "filename": "<filename>",
      "file_base64": "<file_base64>"
    },
    "name": "upload_intake"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
company_idYes
file_base64Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does well: it discloses the 202/queue-row response, the required follow-up poll via get_intake, that mixed .zip files are routed per file, and that unroutable files fail with a reason rather than being silently dropped. It omits permission/auth requirements and any file-size or payload limits, which matter for a base64 upload tool.

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?

Front-loaded with the core purpose, then routing rules, then return/async behavior, in a logical order with no filler sentences. The parenthetical format lists are dense and slightly interrupt the reading flow, but every clause carries 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?

For a three-required-parameter write tool with no output schema, the description covers purpose, routing, accepted formats, synchronous return shape, and the async polling contract. The remaining gap is the undocumented company_id and the absence of size or auth constraints on the upload itself.

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 0%, so the description must compensate. It does explain file_base64 as raw bytes in base64 and implies filename via the accepted extensions list, but company_id is never mentioned and no format or sizing guidance is given for filename beyond the type restrictions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Upload ANY file') plus the decisive behavioral trait that the system auto-classifies via a unified intake queue, which distinguishes it from the specialized sibling uploaders. The web-app location anchor ('Documents > Upload') further pins down what subsystem this is.

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 explicit routing rules: prefer this unless plainly an invoice, always use for bank statements, journal/accounting exports, and financial statements. The 'unless plainly an invoice' clause implies an alternative for invoices without naming it, so the exclusions are directional rather than fully enumerated.

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.

Resources