Skip to main content
Glama

document_pii_scan

Scan PDF documents for PII and sensitive information, then generate a JSON report to support privacy review and compliance checks.

Instructions

Scan document for PII and sensitive information [Input: .pdf | Output: JSON report]

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": {
      "input": "<input>"
    },
    "name": "document_pii_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputNo
scan_ssnNo
scan_ibanNo
scan_emailsNo
scan_phonesNo
scan_credit_cardsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 behavioral burden and only discloses input format and that output is a JSON report. It says nothing about permissions, whether files are stored, how detected PII is handled, or what happens when optional scan flags are omitted.

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 plus an input/output tag; nothing is padded or redundant. It is efficient, though the terseness is part of why information is missing rather than a structural flaw.

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 7-parameter tool with no annotations, no output schema, and zero schema coverage, the definition is substantially incomplete. The one-line description cannot tell an agent how the scan flags combine or what the JSON report contains.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, and the description explains none of the six boolean/categorical parameters such as scan_ssn or output. It only loosely hints that input is a PDF path and output is a JSON report, leaving the defaults and per-flag behavior undocumented.

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 ('Scan document') plus the target of the scan ('PII and sensitive information'), which distinguishes it from generic siblings like pdf_classify_type or office_extract_text. It stops short of naming or contrasting any sibling explicitly.

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?

The bracketed '[Input: .pdf]' establishes an input constraint, but there is no guidance on when to use this versus alternatives, no prerequisites, and no mention of what to do with non-PDF documents. An agent must infer the use case entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.