Skip to main content
Glama

pdf-suite

pdf_redact_terms

Scan PDF text streams for target terms or PII patterns (emails, SSNs, cards) and purge matching raw stream literals + metadata before re-saving.

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_redact_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathNo
base64DataNo
outputPathNo
redactTermsNo

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?

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals that redaction operates on raw stream literals plus metadata and re-saves a file, but omits critical behavior: that the operation is irreversible, whether the source file is modified, which auth/password constraints apply, and how conflicts between inputPath and base64Data are handled.

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?

One front-loaded sentence with no filler; the mechanism and scope come first. It is dense and slightly jargon-heavy ('raw stream literals') but every clause carries information.

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 zero-annotation, zero-schema-documentation, four-parameter mutation tool with no output schema, the description is too thin. It says nothing about the required input source pairing, whether the result reports redaction counts or just a saved path, or what happens when no terms match.

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, so the description must compensate and it does not. It never explains the inputPath vs base64Data alternative source inputs, what outputPath defaults to, or the format/limits of redactTerms — the agent is left guessing the contract.

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 pair (scan/purge) against a specific resource (PDF text streams) with concrete targets ('target terms or PII patterns (emails, SSNs, cards)'). It is clearly distinguishable from siblings like pdf_compliance_audit or pdf_protect_metadata, though it never names an alternative to sharpen the boundary.

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 explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as a compliance-audit tool that might be the better first step. Usage is only inferable from the stated purpose itself.

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