Skip to main content
Glama

Tinplate Edge AI Safety, Security & EU Compliance

tinplate_pii_redactor

Read-onlyIdempotent

PII Redactor API: Mask emails, phones, IBANs, cards, IPs, SSNs, EU VATs, and HU IDs with reversible tokens before LLM calls. (Endpoint: POST /v1/pii-redactor)

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

Input Schema

NameRequiredDescriptionDefault
modeNo'token' returns reversible [PII_<TYPE>_N] tokens + caller-only tokens map; 'mask' returns [REDACTED:<TYPE>] with an empty tokens map.
textYesInput text to scan and redact (max 256 KB).
typesNoOptional whitelist of PII entity types to redact.
localesNoLocale packs to enable (defaults to ['GLOBAL', 'EU']).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / types / items / description
      Added value: +"PII entity category."
  2. Changed1 schema field changed
    • changedInput schema / properties / types / items / enum
      Previous value: -[
      -  "EMAIL",
      -  "CREDIT_CARD",
      -  "IBAN",
      -  "PHONE",
      -  "IPV4",
      -  "SSN",
      -  "EU_VAT",
      -  "HU_TAX_ID",
      -  "HU_TAJ"
      -]New value: +[
      +  "EMAIL",
      +  "CREDIT_CARD",
      +  "IBAN",
      +  "PHONE",
      +  "IPV4",
      +  "IPV6",
      +  "SSN",
      +  "EU_VAT",
      +  "HU_TAX_ID",
      +  "HU_TAJ"
      +]
  3. Changed10 schema fields changed
    • addedInput schema / properties / locales
      Added value: +{
      +  "description": "Locale packs to enable (defaults to ['GLOBAL', 'EU']).",
      +  "example": [
      +    "GLOBAL",
      +    "EU",
      +    "HU"
      +  ],
      +  "items": {
      +    "description": "Locale pack for region-specific PII detectors.",
      +    "enum": [
      +      "GLOBAL",
      +      "EU",
      +      "HU"
      +    ],
      +    "example": "EU",
      +    "type": "string"
      +  },
      +  "maxItems": 3,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / properties / mode / description
      Previous value: -"Parameter 'mode' (e.g. \"token\")"New value: +"'token' returns reversible [PII_<TYPE>_N] tokens + caller-only tokens map; 'mask' returns [REDACTED:<TYPE>] with an empty tokens map."
    • addedInput schema / properties / mode / enum
      Added value: +[
      +  "token",
      +  "mask"
      +]
    • addedInput schema / properties / mode / example
      Added value: +"token"
    • changedInput schema / properties / text / description
      Previous value: -"Parameter 'text' (e.g. \"Customer janos.kovacs@example.hu (IBAN HU4211773016111110180\")"New value: +"Input text to scan and redact (max 256 KB)."
    • addedInput schema / properties / text / example
      Added value: +"Contact Alice at alice@tinplate.dev or +36 30 123 4567. IBAN: HU42117730161111101800000000."
    • addedInput schema / properties / text / maxLength
      Added value: +262144
    • addedInput schema / properties / text / minLength
      Added value: +1
    • addedInput schema / properties / types
      Added value: +{
      +  "description": "Optional whitelist of PII entity types to redact.",
      +  "example": [
      +    "EMAIL",
      +    "IBAN",
      +    "CREDIT_CARD"
      +  ],
      +  "items": {
      +    "enum": [
      +      "EMAIL",
      +      "CREDIT_CARD",
      +      "IBAN",
      +      "PHONE",
      +      "IPV4",
      +      "SSN",
      +      "EU_VAT",
      +      "HU_TAX_ID",
      +      "HU_TAJ"
      +    ],
      +    "example": "IBAN",
      +    "type": "string"
      +  },
      +  "maxItems": 15,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "text",
      -  "mode"
      -]New value: +[
      +  "text"
      +]
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world behavior. The description adds that output tokens are reversible and that the endpoint is POST /v1/pii-redactor, which is useful, but the reversibility detail is also stated in the schema's mode description, so the added value is modest and nothing is said about limits, rates, or where the tokens map is held.

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 economical sentences: purpose first, endpoint reference trailing in parentheses. Nothing is redundant or buried, though the endpoint string is of marginal use to an agent that already has the tool bound.

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 four-parameter, single-purpose redaction tool with full schema coverage and annotations that declare its safety profile, the description conveys enough to call it correctly. No output schema exists, but the mode parameter already documents the return shape (tokens map vs. empty map), so the gap is small.

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?

Schema description coverage is 100% and each parameter, including mode semantics and locale defaults, is fully documented in the schema. The description's enumeration of PII types merely restates the types enum, adding no syntax or behavioral detail beyond structured data.

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

Purpose4/5

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

The description names a specific verb (mask/redact) and enumerates the exact resource classes (emails, phones, IBANs, cards, IPs, SSNs, EU VATs, HU IDs), plus a concrete use case ('before LLM calls'). It does not explicitly distinguish itself from the obvious sibling tinplate_pii_redactor_restore, though 'reversible tokens' implicitly hints at the pairing.

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?

Usage is implied by 'before LLM calls', which tells an agent the intended pipeline position. There is no explicit when-not guidance and no named alternative (e.g., the restore counterpart for reversing tokens), so the agent must infer the workflow.

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