Skip to main content
Glama

Снять пароль

unlock_pdf

Снимает парольную защиту с PDF. file_url: публичный URL защищённого PDF. password: пароль для снятия защиты.

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>",
      "password": "<password>"
    },
    "name": "unlock_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYes
passwordYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true (external fetch), destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description adds that the operation fetches a remote file and needs credentials, but it does not say whether a new unlocked file is produced, whether the original is untouched, or how failures (wrong password, non-encrypted file) are reported.

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 lines, with the action front-loaded and the two parameters listed compactly. No filler; the parameter lines are necessary because the schema has zero descriptions.

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?

An output schema exists, so return values need not be explained, and the tool is simple with two required parameters. Still missing for a credential-handling, network-dependent operation: error behavior on incorrect passwords and whether the source document is modified.

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%, so the description carries the full burden, and it does describe both parameters: file_url is a public URL of the protected PDF, and password is used to remove the protection. The 'public URL' qualifier adds a real constraint absent from the schema, though it does not specify URL format or whether a password can be omitted for owner-only restrictions.

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?

The description states a specific verb and resource: removing password protection from a PDF. This clearly distinguishes it from protect_pdf and other document-processing siblings. It does not explicitly name the inverse sibling protect_pdf, so sibling differentiation is implied rather than stated.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives (e.g., protect_pdf, repair_pdf for damaged/unreadable files). No prerequisites are stated beyond the params, and there is no mention of what happens if the password is wrong or the PDF is not encrypted.

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.