Skip to main content
Glama

Docflare

Upload a document

upload_document

Creates a draft document from a PDF or a Word file (.docx) in the current Docflare workspace. The file comes from one the user attached in the chat (file), from a public https link (url), or, with neither, through a one-time upload link in the answer that takes the file as a multipart POST field named file, once, for 10 minutes; when sending the file there is blocked, or the user has no file in the chat, open_upload_pad lets them drop the file into the chat instead. Docflare checks the file the way a web upload is checked, and turns a Word file into a PDF. The answer is the new draft, the text already on its pages with ids, and its lines: the blank lines where a field can sit, each with an id, its page, its position as a share of the page width and height, and the text beside it. Who gets the draft is set with prepare_document, and fields go on with edit_document. With flow sign-document the user signs the document themselves: every field is theirs, and the people added with prepare_document get the signed copy.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upload_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public https link that opens the PDF or Word file (.docx) itself.
fileNoA PDF or Word file (.docx) the user attached in the chat, as the chat app passes it.
flowNoget-signature when other people sign the document, sign-document when the user signs it themselves and sends the signed copy. get-signature when left out; prepare_document can switch it later.
nameNoThe name of the new document. The file name when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses DOCX-to-PDF conversion, web-style file checking, the 10-minute one-time multipart upload flow, and the exact shape of the returned draft with page text, blank field lines, ids, and positions. It also explains the sign-document flow and who receives the signed copy.

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 purpose is front-loaded and nearly every clause carries useful information. However, the long run-on sentences and dense parentheticals make the definition harder to scan than necessary.

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?

For a complex upload tool with no output schema, the description covers input sources, fallback routing, validation and conversion behavior, the return payload, downstream field preparation, and signing semantics. An agent has enough context to call it correctly.

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 description coverage is 100%, so the schema already documents all four parameters. The description reinforces the file, url, and flow behavior, but adds limited detail about the name parameter beyond the schema.

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: creates a draft document from a PDF or .docx in the current workspace. It distinguishes upload_document from downstream operations such as prepare_document and edit_document.

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?

Explicitly explains the three input routes: chat attachment (file), public https link (url), or a one-time upload link when neither is available. It names open_upload_pad as the fallback when sending the file is blocked or the user has no chat file.

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