Skip to main content
Glama

Восстановить PDF

repair_pdf

Восстанавливает повреждённый PDF, который не открывается или открывается с ошибкой. 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": "repair_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so safety profile and the external fetch are covered. The description adds only that a publicly reachable URL is required; it does not say whether the repair produces a new file, where the result is delivered, or what happens when repair fails, which is meaningful added context for a repair operation.

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?

Two short sentences with the condition front-loaded ahead of the parameter note; nothing is redundant. The parameter note is slightly terse and could have been folded into a clearer form, but the structure is efficient.

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

Completeness3/5

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

For a one-parameter tool with an output schema (return values need not be described) and full annotation coverage, this is close to adequate. What is missing is what an agent would still want: whether the source file is modified, whether there are file-size/page limits on repair, and how to tell an unrepairable file from a successful run.

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 0%, so the single untyped 'string' parameter relies on the description, and the line 'file_url: публичный URL PDF-файла' usefully adds that the URL must be publicly accessible and must point at a PDF. It still omits practical constraints (http/https only, size limits, redirects), so the schema gap is only partially compensated.

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 ('Восстанавливает повреждённый PDF') plus the trigger condition ('не открывается или открывается с ошибкой'). That distinguishes it from most siblings (compress_pdf, unlock_pdf, flatten_pdf), though it does not explicitly contrast with the closest neighbour, unlock_pdf, so it stops short of a 5.

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?

The failure symptom ('won't open or opens with an error') implies when to reach for this tool, which is genuine usage context. However there is no explicit exclusion — nothing tells the agent to use unlock_pdf for password problems or flatten_pdf for rendering issues — so the guidance remains implied.

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.