Skip to main content
Glama
omitly

omitly-mcp

Official
by omitly

find_sensitive_regions

Scan a PDF on-device to find candidate PII regions—emails, SSNs, phone numbers, card numbers, and Australian IDs—returning page coordinates for redaction. No file upload.

Instructions

Scan a PDF on-device and return candidate regions that look like PII — emails, US SSNs, phone numbers, card numbers, and Australian identifiers (TFN, ABN, ACN, Medicare, Centrelink CRN, IHI, BSB; kinds 'tfn'/'abn'/'acn'/'medicare'/'crn'/'ihi'/'bsb') — each with the page and exact coordinates (in PDF points) the redaction engine needs. Use this FIRST so you select regions by entity ('redact every TFN') and pass the returned coordinates straight to redact_pdf, instead of guessing geometry from a rendered page. Numeric kinds are check-digit validated where a published algorithm exists (CRN has none — its matches are format-only). Candidates are best-effort pattern matches for review — not a completeness guarantee and not a compliance assessment; the file is never uploaded — detection runs locally. Each candidate carries a MASKED preview (e.g. '•••-••-6789'), never the raw value: the secret stays on the machine. You don't need the plaintext to redact — drive it by page + coordinates. (A human reviewer has the file open locally for full context.) Free tier (no native engine): results are EVALUATION-marked and limited to a monthly number of free checks, counted locally — past the cap this tool returns a structured 'free-cap' refusal. A configured licensed engine is not capped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pdfPathYesabsolute path to the PDF to scan
regionsNonarrow LISTED pattern kinds to these regional packs (generic kinds always listed; confirmed under-mark survivors always report); omit to scan everything — the safe default

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
countYes
regionsYes
evaluationNo
Behavior5/5

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

With no annotations provided, the description carries full burden and fully delivers: it discloses local/on-device processing, no upload, masked previews, best-effort/no-guarantee nature, check-digit validation, CRN format-only, and free-tier cap behavior with EVALUATION-marked results. This is a comprehensive transparency disclosure.

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?

The description is front-loaded with purpose and is well-structured, but it is long and contains slight redundancy (e.g., 'never uploaded' and 'secret stays on the machine'). Still, every sentence contributes meaningful information for a complex tool.

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

Completeness5/5

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

Given the tool's complexity (free-tier cap, security, coordinates, PII types) and the existence of an output schema, the description is complete: it covers behavior, limitations, security, and workflow. It does not need to explain return values because the output schema exists.

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 covers both parameters with descriptions (100% coverage), so baseline is 3. The description adds value by explaining how to use regions ('select regions by entity') and that coordinates are directly usable by redact_pdf, providing semantic context beyond the schema, though it does not add new parameter-level details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool scans a PDF and returns candidate PII regions with page and coordinates, and explicitly contrasts it with redact_pdf ('Use this FIRST... instead of guessing geometry from a rendered page'). This identifies the verb, resource, and output, and distinguishes it from siblings like locate_text and redact_pdf.

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

Usage Guidelines5/5

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

The description gives explicit workflow guidance: use this tool first to select regions by entity, then pass coordinates to redact_pdf. It also clarifies the free-tier cap and structured refusal, and notes that plaintext is not needed. This clearly communicates when and how to use the tool versus alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/omitly/omitly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server