Skip to main content
Glama

privacidad_anonimizar_documento

Read-only

Anonymize Chilean personal data such as RUT, emails, phone numbers, bank accounts, addresses, and names in legal documents, then reverse it with a local map.

Instructions

Anonimiza de forma reversible datos personales chilenos (RUT verificado Módulo 11, emails, teléfonos, cuentas bancarias, domicilios y nombres en contexto procesal) bajo la Ley N.° 21.719 y Art. 247 CP, o revierte un texto con su mapa local.

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": {
      "texto": "<texto>"
    },
    "name": "privacidad_anonimizar_documento"
  }
}

Input Schema

NameRequiredDescriptionDefault
textoYesTexto jurídico o extracto de expediente a anonimizar o desanonimizar
accionNo'anonimizar' (defecto) o 'desanonimizar'anonimizar
usar_presidioNoActiva enriquecimiento NER opcional con Microsoft Presidio si está instalado
mapa_reversionNoMapa {token: valor_real} requerido solo cuando accion='desanonimizar'
incluir_personasNoSi es True, enmascara nombres propios tras tratamientos (don/doña/Sr./menor)
incluir_domiciliosNoSi es True, enmascara domicilios particulares

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds substantive context beyond them: the transformation is reversible, RUT validation uses Módulo 11, and reversal consumes a locally held map. It stops short of saying whether the map is returned by the tool or must be persisted by the caller.

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?

A single front-loaded sentence opening with the action verb, enumerating scope, then pivoting to the inverse operation. Every clause carries information; nothing is repeated from the title or schema.

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?

With no output schema, the description is the only source for what the agent receives back, and it never states that the anonymized text and the reversal map are returned together. The optional Presidio NER path and the default booleans are left entirely to the schema. Adequate for a six-parameter tool but leaves a meaningful return-shape gap.

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%, so all six parameters including the accion enum and the nested mapa_reversion object are already documented. The description reinforces the coupling between reversibility and the local map and names the PII categories that correspond to incluir_personas and incluir_domicilios, but adds no format or syntax detail beyond the schema. Baseline 3 applies.

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 ("Anonimiza") plus its inverse ("revierte") against a precisely scoped resource: Chilean personal data, enumerated by category (RUT with Módulo 11 verification, emails, phones, bank accounts, addresses, names in procedural context). The legal framing (Ley N.° 21.719, Art. 247 CP) further pins the domain so it cannot be confused with the ARCO sibling.

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?

The description implies usage (legal texts and case-file extracts) and signals that reversal requires the local map, which is genuine conditional guidance. However, it never states when to prefer this over alternatives or when not to use it, and no explicit exclusions or prerequisites (e.g. map retention) are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools