fynk MCP

Create document PDF upload URL

create-document-pdf-upload-url

Create a signed URL that a single PDF can be POST-uploaded to, for later use with create-document-from-pdf-upload.

Use this tool when:

The user wants to create a document from an existing PDF file and you need somewhere to upload it to first

Returns a uuid (pass it to create-document-from-pdf-upload after the upload completes), a url (target of the POST request), a fields map to send as form fields in the POST body before the file itself, and an expires_at timestamp after which the URL stops working.

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": "create-document-pdf-upload-url"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`url`	No	Perform a multipart/form-data POST request to this URL to upload the PDF
`uuid`	No	Send this UUID to create-document-from-pdf-upload AFTER uploading the file to the given URL
`fields`	No	Form fields to send in the POST body, before a final "file" field holding the PDF contents
`expires_at`	No	When the URL stops being usable

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false. The description adds useful behavior beyond that: the URL is signed, supports a single PDF POST upload, includes form fields to send before the file, and expires at a given timestamp. It does not cover authentication requirements or rate limiting, so it falls short of a 5.

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 front-loaded with the core action and use case, then provides a compact bullet and return-value summary. It is slightly longer than necessary because it describes return values even though an output schema exists, but the information is still relevant for chaining to the next tool.

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 no-parameter tool with an output schema and relevant annotations, the description provides everything an agent needs: when to call it, what it returns, how to use the POST fields, and which sibling tool consumes the uuid afterward. No critical context for correct invocation is missing.

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?

The tool has zero input parameters, so there is no parameter semantics to explain. The baseline for a no-parameter tool is 4, and the description correctly focuses on the upload flow rather than inventing parameter details.

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 specific verb and resource: creating a signed URL for a single PDF upload. It also explicitly names the downstream sibling create-document-from-pdf-upload, making the tool's role easy to distinguish from related document-creation tools.

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 an explicit use case: when the user wants to create a document from an existing PDF and needs an upload target first. It also explains the alternative flow by saying to pass the returned uuid to create-document-from-pdf-upload after the upload completes.

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

All fynk MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?