Skip to main content
Glama

Potential PII exposure detector

privi_pro_pii_presence
Read-only

Count email, telephone and Social Security number patterns without revealing matches. PAID ONLY: 5 prepaid credits; production billing required.

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": {
      "text": "<text>"
    },
    "name": "privi_pro_pii_presence"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that — matches are not returned, and invocation costs 5 prepaid credits with production billing required — but says nothing about output shape, rate limits, or how partial/ambiguous matches 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the capability and its privacy guarantee, followed by the cost gate. Nothing is wasted and the ordering puts the most decision-relevant fact first.

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?

The tool is simple and has no output schema, so the description should at least sketch what comes back — per-pattern counts, a total, or both. It implies counts per PII type but leaves the return shape and the handling of overlapping matches unspecified.

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

Parameters3/5

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

One parameter with 0% schema description coverage, so the schema contributes nothing about what 'text' should contain. The description implies the text to be scanned but does not state size limits, whether it is raw document text or a pre-extracted field, or any encoding expectations.

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?

States a specific verb and resource — counting email, telephone and SSN patterns in supplied text — plus a distinguishing behavioral trait: matches are never revealed. An agent can immediately tell this is a detection/counting tool, distinct from the reconciliation, drift and integrity siblings.

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?

No when-to-use guidance, no exclusions, and no alternatives named. The only conditional information is the billing constraint, which gates access rather than helping the agent choose this tool over another.

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.