Skip to main content
Glama

KDAN PDF

by com.kdandoc.mcp

Create PDF Upload Page

create_upload_page

Display an interactive PDF upload widget directly in the chat.

Use this when the user wants to upload a local PDF file from their device. This is the standard upload method for MCP clients (e.g. Claude) where file attachments with download URLs are not available.

Do NOT call upload_pdf when using this tool — the widget handles the upload automatically. The widget renders inline and the PDF viewer appears after the user selects a file. Do NOT call view_pdf after this tool; the widget manages the UI. Never tell the user the file is still uploading; the widget handles the spinner.

After the user uploads via the widget and notifies you, call check_upload_status(session_id=) to discover the uploaded file and its job_id before proceeding with any operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idNoExisting session ID to continue an ongoing workflow. If omitted, a new session is created. Always pass the same session_id throughout the entire conversation to keep all files grouped together.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
reply_noteYes
session_idYes
upload_urlYes
instructionsYes
upload_tokenYes

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations, the description details widget behavior: automatic upload handling, inline rendering, spinner management, and user notification protocol. No contradiction with annotations.

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?

Well-structured with front-loaded purpose and clear sections. Slightly verbose but every sentence earns its place. Could be slightly more concise.

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?

The description covers the entire workflow: when to use, what it does, what not to do, and what to do next. Given the complexity and presence of output schema, it is fully complete for correct tool invocation.

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

Parameters5/5

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

The description adds practical context for the session_id parameter: 'Always pass the same session_id throughout the entire conversation to keep all files grouped together.' Schema coverage is 100% but description enhances understanding.

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 the tool's purpose: 'Display an interactive PDF upload widget directly in the chat.' It distinguishes from sibling tools like upload_pdf and view_pdf by explicitly instructing not to call them.

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?

Explicit usage guidance: 'Use this when the user wants to upload a local PDF file from their device.' Includes clear 'do NOT' instructions for sibling tools and post-usage steps like calling check_upload_status.

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

All KDAN PDF toolsInspect
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.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: uploads are split by context (single, batch, widget), content inspection is split by method (text, images, redaction lines), and password operations are split by state (set vs change). Descriptions explicitly cross-reference to prevent confusion.

Naming Consistency4/5

All tools start with a verb (upload, check, compare, compress, create, delete, get, list, redact, set, change, view), but the position of 'pdf' varies (suffix in compress_pdf, middle in get_pdf_info) and some names are compound like 'batch_upload_pdf' and 'get_latest_comparison'. Pattern is readable but not perfectly uniform.

Tool Count4/5

16 tools is slightly above the ideal 3-15 range, but each tool maps to a distinct operation or workflow step in PDF handling. The count feels justified given the breadth of features (upload, compress, delete, password, redact, compare).

Completeness4/5

The surface covers the core PDF lifecycle: upload, view, compress, delete pages, password protection, redaction, and comparison. Minor gaps exist (no merge, split, or rotate), but the primary workflows are fully supported with mandatory pre/post checks.

Resources