Skip to main content
Glama
talonicdev

talonic-mcp

Official
by talonicdev
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Request File Upload

talonic_request_upload

Request a file upload URL and document ID when you can't deliver the file directly due to size or sandbox restrictions.

Instructions

STATUS: stable.

Request a file upload link for the user. Use this when the user wants to extract a file but you cannot deliver it directly (e.g., the file is too large for tool-call arguments, or you're running in a sandboxed environment like Claude.ai).

Returns an upload URL the user can open in their browser to drop the file, plus a document_id to track the upload.

After showing the URL to the user, poll with talonic_get_document until status is 'completed' (the file has been uploaded, OCR'd, and is ready for schema-specific extraction). Then call talonic_extract with the document_id and a schema or schema_id.

IMPORTANT: a user message like 'uploaded', 'done', or 'I dropped it' only confirms the browser-side upload finished. It is NOT a signal that server-side processing is complete. The document still needs OCR and exhaustive extraction (typically 10-30 s after the browser upload). You MUST poll talonic_get_document yourself until status is 'completed' regardless of what the user says. Calling talonic_extract before status is 'completed' may return errors.

USE WHEN:

  • The user has a file to extract but you cannot send it via tool-call arguments (e.g., file is larger than ~32KB, or the environment blocks outbound data).

  • You are running in a hosted/sandboxed environment (Claude.ai, ChatGPT) where file_data cannot be used reliably.

  • The user explicitly asks for an upload link.

DO NOT USE WHEN:

  • You can deliver the file directly via file_data (local-stdio installs with small files).

  • The file is already accessible via a public URL (use file_url on talonic_extract instead).

  • The document is already in the workspace (use document_id on talonic_extract instead).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYesThe name of the file being uploaded, including extension (e.g. 'invoice.pdf'). Used to pre-allocate the document and infer MIME type.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
document_idYesThe pre-allocated document ID. Use with talonic_get_document to poll status, and with talonic_extract once uploaded.
upload_urlYesURL the user should open in their browser to drop the file.
expires_atYesISO 8601 timestamp when the upload link expires.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations show readOnlyHint=false and openWorldHint=true. The description discloses that it returns an upload URL and document_id, warns against relying on user messages for completion, and mandates polling talonic_get_document until status 'completed'. It also notes possible errors if talonic_extract is called too early, providing full behavioral context beyond annotations.

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?

The description is well-structured with a STATUS line, a clear purpose statement, and bullet-pointed 'USE WHEN' and 'DO NOT USE WHEN' sections. Every sentence adds value, and it is appropriately sized without being verbose.

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?

Given the complexity (request, poll, then extract), the description is complete: it explains the flow, return values, what to do after showing the URL, and references sibling tools. The existence of an output schema covers return value details, so no further explanation is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with one parameter 'filename' described in schema. The description adds value by explaining that it's used to 'pre-allocate the document and infer MIME type', which goes beyond the schema's basic description. Therefore, it scores above the baseline of 3.

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?

The description clearly states it requests a file upload link for the user, specifying the verb 'request' and resource 'file upload link'. It distinguishes from siblings by explaining when to use this tool (e.g., when file is too large for direct tool-call arguments).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description provides explicit 'USE WHEN' and 'DO NOT USE WHEN' sections, listing specific conditions and alternatives like file_url or document_id. It also contrasts with sibling tools like talonic_extract, giving clear guidance on when to use this tool versus alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/talonicdev/talonic-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server