Skip to main content
Glama

pdf-suite

pdf_protect_metadata

Audit PDF encryption state, scrub identifying Creator/Producer/Author metadata, and stamp deterministic integrity protection headers.

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": "pdf_protect_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathNo
base64DataNo
outputPathNo
ownerLabelNoProtected Document

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and does not meet it. It never says whether the input file is modified in place or written to outputPath, whether the original is preserved, what 'scrub' irreversibly destroys, or whether the operation requires an unencrypted source document. The mixing of an 'audit' (read) with 'scrub' and 'stamp' (write) in one sentence is never clarified.

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?

A single front-loaded sentence with three parallel verbs and no filler; every clause carries information. It loses a point only because the third clause is impenetrable enough that brevity shades into under-specification.

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

Completeness2/5

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

For a four-parameter, zero-coverage, annotation-free tool with no output schema, this is thin. The agent gets no input-selection logic, no side-effect disclosure, and no idea what the 'audit' portion returns, which is the minimum needed to invoke this safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, and the description mentions none of them by name or meaning. It gives no hint about the inputPath vs base64Data alternative, what outputPath controls, or what ownerLabel does in the stamped header, so an agent must guess the calling contract entirely from bare property names.

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 names three concrete operations on a concrete resource: auditing encryption state, scrubbing Creator/Producer/Author metadata, and stamping integrity headers. That is far more specific than the tool name alone. It stops short of distinguishing itself from plausible siblings such as pdf_compliance_audit or pdf_redact_terms, and 'stamp deterministic integrity protection headers' is opaque jargon that leaves unclear whether real encryption is applied.

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 statement of when to pick this tool over pdf_compliance_audit (which also sounds like an audit) or pdf_redact_terms (which also removes identifying content). No preconditions, no exclusions, and no indication of whether this is a read-only audit, a mutation, or both combined in one call.

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.

Resources