Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

PII detection and redaction: emails, phones, cards, IBANs

text_pii
Read-only

Find personal data in a text and get it back redacted: emails, phone numbers, card numbers (Luhn-checked), IBANs (mod-97), US SSNs, IP and crypto wallet addresses, each with its position, plus the text with every hit replaced by a label such as [EMAIL]. Hits are shown masked. Up to 20,000 characters; names and street addresses are not detected. Use before logging, storing or sending text to a model. Example: text=Contact Anna at anna.berg@example.com or +46 70 123 45 67; card 4111 1111 1111 1111.. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text to scan (up to 20,000 characters)
typesNoOptional comma-separated types to look for: email, iban, credit_card, us_ssn, crypto_address, ip_address, phone (default all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/destructive annotations: discloses the 20,000-character cap, that hits are returned masked with positions, the pricing model ($0.01/call via x402 USDC or card key), 25 free calls, that failed calls are free, and that repeats are billed. This is exactly the cost/limit context an agent needs before calling.

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?

Front-loaded with the core verb and output shape, and every clause carries information. The billing details are packed into a single run-on second half, which slightly hurts scanability but nothing is truly wasted.

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?

With no output schema, the description carries the return-value burden itself and does: positions per hit, masked hits, and the labeled redacted text such as [EMAIL]. Limits, non-detected entity classes, and cost are all covered, so an agent has everything needed to call it correctly.

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 coverage is 100%, so the baseline is 3; the description adds value by explaining that results come back masked with positions and by giving a concrete multi-type example input. It does not spell out the exact comma-separated token values for the `types` parameter, so it stops short of a 5.

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+resource ('Find personal data in a text and get it back redacted') and enumerates exactly what is matched (emails, phones, Luhn-checked cards, mod-97 IBANs, SSNs, IPs, wallet addresses). The text-scoped nature separates it from the domain/email lookup siblings without needing to name them.

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

Usage Guidelines4/5

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

Gives an explicit trigger: 'Use before logging, storing or sending text to a model.' It also states a scope exclusion ('names and street addresses are not detected'). No named alternative tool or when-not-to-use-this alternative, so not a 5.

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.