Skip to main content
Glama

Convert text by replacing personal data with placeholders

redact
Read-only

Replaces personal data in a text with placeholders: e-mail addresses, phone numbers, IBANs (mod 97 checked), payment card numbers (Luhn checked only), IPv4 addresses and, with names true, person names found by the chat model. Returns the redacted text and counts per type. Original values are never returned. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
textYesText, up to 20,000 characters
namesNotrue to also replace person names (uses the chat model)
typesNoAny of email, phone, iban, card, ip (default all)

Output Schema

NameRequiredDescriptionDefault
textNo
countsNo
sourceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnly and openWorld; the description adds substantial context beyond that: originals are never returned, per-type counts come back, card detection is Luhn-only (weaker guarantee than IBAN mod 97), and names rely on the chat model (non-deterministic). It also discloses the x402 payment model, $0.002 per successful call, and that failed calls are free — real pre-invocation facts. No annotation conflict.

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?

Two dense sentences, front-loaded with what is replaced, then behavior/return/pricing. Nearly every clause earns its place; the only soft spot is the vague "and 10 more networks" phrasing, which reads as marketing filler rather than actionable detail.

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?

For a three-parameter, read-only transform with a 20,000-character input limit, the description covers inputs, detection semantics, output shape (redacted text plus per-type counts), data-handling guarantee, and billing preconditions. An output schema exists, so not enumerating the return structure further is fine.

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, but the description adds meaning the schema lacks: the `names` flag maps to chat-model inference rather than a deterministic matcher, and `types` values are validated with different rigor per type. The `types` default (all) is also stated, which the schema implies only loosely.

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?

Names a specific verb and resource ("Replaces personal data in a text with placeholders") and enumerates exactly which entity classes are covered, including validator caveats (mod 97, Luhn only). An agent can tell immediately what this does and what it does not detect.

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

Usage Guidelines3/5

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

Implies usage through the call description and the `names` / `types` switches, and notes `names` invokes the chat model (a cost/behavior tradeoff). It never states when to prefer this over alternatives (e.g. using `chat` to sanitize manually) or when redaction is inappropriate, so guidance stays implicit.

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