Skip to main content
Glama

APEX AI, LLM, Embeddings, OCR & Media

Pii redact

pii_redact
Read-onlyIdempotent

Detect and redact private keys, API tokens, JWTs, emails, IBANs, SSNs, phones, IPs, and Luhn-validated payment cards before LLM logging or sharing ($0.001). $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to scan and redact PII/secrets from (up to 32000 chars)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered; the description adds the non-obvious behavioural facts: a monetary cost ($0.001 per call), an x402 payment handshake over USDC/XNT on named chains, and a required first call to fetch terms. It stops short of describing what the response contains, which matters since there is no output schema.

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 capability and scope, then pricing, then the call sequence — a sensible ordering with no filler sentences. The payment/chains clause is dense and slightly jargon-heavy, but every sentence carries information an agent needs.

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

Completeness4/5

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

For a two-parameter tool with full schema coverage and no output schema, the description covers scope, cost, and the payment protocol sequence. The one meaningful gap is return shape — whether it returns redacted text, a findings list, or both — which the agent must discover by calling.

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 would be 3, but the description adds real meaning the schema does not convey: `payment` is not an ordinary argument but the second half of a two-phase purchase (omit it first to get terms, then pass a signed payload). That workflow semantics is what an agent needs to use the parameter correctly.

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 ('Detect and redact') and enumerates exactly what classes of data are targeted: private keys, API tokens, JWTs, emails, IBANs, SSNs, phones, IPs, and Luhn-validated cards. It also states the motivating use case ('before LLM logging or sharing'), so an agent knows precisely what the tool is for without consulting siblings.

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 clear situational guidance ('before LLM logging or sharing') and an explicit operational prerequisite: call once without `payment` to receive terms, sign with your own wallet, then call again with `payment`. It does not name a when-not case or an alternative tool, but for a narrowly scoped redaction utility the positive guidance is sufficient.

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.