Skip to main content
Glama
Sign In

fynk MCP

by com.fynk.app
OverviewDiscussionsAdmin

Get latest document PDF URL

get-latest-document-pdf-url
Read-onlyIdempotent

Get a download URL for the latest revision of a document as a PDF.

Use this tool when:

  • The user wants to download the current state of a document as a PDF

  • You need a PDF link to share with the user for review

Returns the URL as plain text. The URL is short-lived; fetch a new one if it expires before download.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "document_uuid": "<document_uuid>"
    },
    "name": "get-latest-document-pdf-url"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_uuidYesUUID of the document to fetch the PDF for. If you don't already have the document's UUID, use the list-documents tool to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the return is plain text, and the URL is short-lived so a new one must be fetched after expiry. It does not discuss permission requirements or what happens when no PDF revision exists.

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?

Front-loads the core action in one sentence, then uses a tight bulleted when-to-use list and closes with return/expiry notes. The bullets largely restate the opening sentence, which is mild redundancy, but nothing is confusing or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with annotations and no output schema, the description covers purpose, when to use, return type, and the URL expiry caveat. Only edge behavior (e.g., document without a PDF revision, or error conditions) is unaddressed, which is minor.

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% and the document_uuid parameter already documents itself, including the pointer to list-documents when the UUID is unknown. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 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?

States a specific verb (get) and resource (download URL for the latest revision of a document as a PDF), including the key qualifier that it is the latest revision. This is clearly distinguishable from sibling tools like get-document-info or create-document-pdf-upload-url without opening a schema.

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

Usage Guidelines4/5

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

Provides an explicit 'Use this tool when' section with two concrete scenarios: downloading the current state and obtaining a shareable link for review. It lacks explicit exclusions or named alternatives (e.g., when to use get-document-info instead), so it falls short of a 5.

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

All fynk MCP toolsInspect
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