Well

Create statement upload slot

well_create_statement_upload

Mint a one-time, short-lived upload slot for a bank-statement file.

Use this when the user has a statement file (PDF, or a large CSV/XML) to import; the file's bytes do not travel through the model. It returns a single-use upload URL + token; the client (or the user) POSTs the raw file bytes to that URL, and the resulting document enters the exact same import pipeline as an in-app upload (detection, dedup, promotion).

This result renders a card in widget-capable hosts right away — do not wait for a poll to make it appear. Once the client has uploaded the file bytes, call well_get_statement_import_result with the document_id below ONE time to learn the outcome. The card refreshes itself as extraction and promotion complete, so a repeated poll only serves your own narration in chat, never the card's rendering.

The token authorizes exactly ONE upload to this workspace and expires in 15 minutes. It is burned on first use — a second upload needs a new slot. It cannot be used for anything other than a statement upload.

The response's document_id is PRE-ALLOCATED at mint time — the upload has not happened yet, and this exact id is what the document will carry once it does. A call to well_get_statement_import_result before the upload lands is a normal "not_found_yet", not an error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`workspace_id`	No	Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
`idempotency_key`	No	Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`token`	No
`success`	Yes
`upload_url`	No
`document_id`	No	The pre-allocated document id — poll well_get_statement_import_result with it.
`expires_in_seconds`	No

TDQS

A4.4/5.0

Behavior5/5

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

Discloses one-time token burn, 15-minute expiry, single-workspace authorization, pre-allocated document_id, 'not_found_yet' semantics before upload, and the card auto-refresh behavior that eliminates the need for polling. This far exceeds what the annotations convey and materially affects how an agent should invoke and follow up.

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?

The description is multi-paragraph but every block earns its place: purpose, usage conditions, lifecycle constraints, and preallocation semantics. Some repetition around polling and card rendering exists, but it is not padded overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the full lifecycle: mint URL/token, POST raw bytes, call result exactly once, card rendering behavior, expiry and burn, and pre-upload result semantics. Given that an output schema is present, nothing needed for correct use is missing.

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?

Input schema coverage is 100%, so the baseline is 3. The description reinforces that workspace_id may be omitted when the token authorizes one workspace, but it does not add significant parameter-level meaning beyond the schema's existing descriptions.

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 ('Mint') and resource ('one-time, short-lived upload slot for a bank-statement file'), which clearly distinguishes it from the many sibling create_* tools and from well_get_statement_import_result. The title alone is generic, but the description anchors the tool precisely.

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?

Explicitly says to use this when the user has a statement file (PDF, large CSV/XML) to import and notes that the file bytes do not travel through the model. It also prescribes the follow-up call to well_get_statement_import_result once, but it does not name an alternative tool or explicitly state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Well tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: CRUD for companies, people, and invoices; financial analytics (cash, cost, runway, holdings); connector management and invocation; schema discovery; querying; reconciliation; and contact channel management. No two tools could be confused for the same action.

Naming Consistency5/5

All tools follow the `well_verb_noun` pattern with consistent verb choices (create, get, list, update, delete, add, remove, run, resolve, query, invoke). The naming is predictable and makes the tool's purpose immediately clear.

Tool Count4/5

With 26 tools, the set is slightly above the ideal 3-15 range, but every tool earns its place given the breadth of the domain (CRM, invoicing, financial analytics, reconciliation, connector management). The count is well-scoped and not excessive.

Completeness4/5

The tool surface covers core CRUD, financial KPIs, reconciliation, and connector management. Minor gaps exist (e.g., no direct tool to update contact channels or manage accounts), but the query and schema tools allow agents to work around them, and the primary workflows are fully supported.

Resources

Need Help?