Skip to main content
Glama

Сгладить PDF

flatten_pdf

Сглаживает PDF (flatten): впечатывает поля форм и аннотации в страницы. Результат нельзя редактировать — идеально для госорганов и печати. file_url: публичный URL PDF-файла.

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": {
      "file_url": "<file_url>"
    },
    "name": "flatten_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses the key behavioral trait: the output becomes non-editable, which is the whole point of the operation. It doesn't contradict the annotations and adds real context about the resulting artifact. It still omits whether the source file is preserved and whether password-protected PDFs are supported, keeping it 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?

Three short sentences, front-loaded with the action, then the consequence, then the parameter. Nothing is padded. A line break separating the parameter note from the behavior description would make the structure slightly cleaner.

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?

A single-parameter transformation tool with an output schema, so return values need no explanation. Purpose, effect, output immutability, and the parameter's URL requirement are all covered. Minor gaps remain around source-file preservation and input limits, which are secondary for a tool this simple.

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?

Schema description coverage is 0% — the schema only says type string with no description — so the description must carry the meaning, and it does: file_url is a *public URL* to the PDF. That constraint (publicly reachable, not a local path or private link) is the one thing an agent could plausibly get wrong, and it is stated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (flatten a PDF) and immediately explains the mechanism: form fields and annotations are baked into the pages. That is far more informative than the title alone. It doesn't name a sibling or contrast with edit_pdf, but no sibling performs flattening, so disambiguation is not a real risk.

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

Usage Guidelines3/5

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

"Ideal for government agencies and printing" implies the intended use case (final output, submission, print), but it never states when NOT to use it or points to edit_pdf / pdf_to_pdfa as alternatives. The guidance is suggestive rather than explicit.

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.