Skip to main content
Glama

Docflare

Open the upload pad

open_upload_pad
Read-only

Shows a box in the chat where the user drops a PDF or a Word file (.docx), or picks one from their device, and Docflare makes it a draft the way upload_document does. Use it when sending the file to the upload_document link is blocked, for example with HTTP 403, or when the user has no file in the chat. Ask the user to drop the file there and reply once it is uploaded. The pad then gives you the new document id; without it, the newest draft in document_status is the one. Read its text and lines with get_document, then carry on with prepare_document and edit_document.

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": "open_upload_pad"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds genuinely useful behavior beyond them: the required ask-the-user-and-wait interaction, how to obtain the new document id, and the fallback of taking the newest draft from document_status. There is a mild tension in that the pad 'makes a draft' (a state change) while readOnlyHint=true, but that is consistent with reading the tool call itself as opening a UI surface that the user then completes. It does not describe what happens if the user never uploads or how the pad is dismissed.

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?

It is front-loaded with the core action and then moves through fallback condition, user interaction, result handling, and follow-up steps in a logical order; nearly every sentence carries operational information. It is on the longer side, and the chain of follow-on tools (get_document, prepare_document, edit_document) could be compressed, but nothing is filler.

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 tool with no output schema, the description supplies everything an agent needs: why to call it, what the user must do, how to recover the document id, and which tools to use next. The remaining ambiguity (what if the user never uploads) is minor for a UI-opening tool.

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% and the single `flow` parameter has a self-documenting enum with a stated default, so the schema carries the semantics. The description never mentions `flow` at all, so it adds no meaning beyond the schema — baseline 3 is appropriate.

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 states a concrete action and resource: it opens a chat box where the user drops a PDF or .docx, and Docflare turns that file into a draft equivalent to upload_document. It also distinguishes this from the sibling upload_document by framing the pad as the fallback path, so an agent can tell the two apart without opening either schema.

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?

It gives explicit trigger conditions: use it when the upload_document link is blocked (e.g. HTTP 403) or when the user has no file in the chat. It names the alternative and the exact circumstances that select this tool, leaving nothing to inference.

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