Skip to main content
Glama

privacidad_tramitar_arco

Read-only

Generate official Chilean responses to ARCO data rights requests (access, rectification, cancellation, opposition) under the Personal Data Protection Law.

Instructions

Procesa y genera el modelo oficial de respuesta a solicitudes de Derechos ARCO bajo la Nueva Ley de Protección de Datos Personales.

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": {
      "tipo_derecho": "<tipo_derecho>",
      "solicitante": "<solicitante>",
      "rut": "<rut>",
      "datos_solicitados": "<datos_solicitados>"
    },
    "name": "privacidad_tramitar_arco"
  }
}

Input Schema

NameRequiredDescriptionDefault
rutYesRUT del solicitante
solicitanteYesNombre del titular de los datos
tipo_derechoYesDerecho a ejercer ('ACCESO', 'RECTIFICACIÓN', 'CANCELACIÓN', 'OPOSICIÓN')
datos_solicitadosYesDescripción de los datos requeridos

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

B3.3/5.0
Behavior3/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 that a standardized official response template is produced, which is meaningful context beyond the annotations. It does not disclose however whether the request is registered/stored, whether the output requires legal review, or how generation interacts with the readOnly claim.

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 with no filler, restating neither the name nor the schema. Every clause earns its place by naming the action, the input class, and the output artifact.

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?

The description names the tool's output (the official response model), which partially compensates for the missing output schema. But it leaves out the procedural context an agent needs for a compliance action: applicable deadlines, whether a response is persisted, and whether the generated model is advisory or binding.

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%: all four parameters (rut, solicitante, tipo_derecho, datos_solicitados) are documented in the schema, including the four allowed tipo_derecho values. The description adds nothing about parameter meaning or format, so the baseline 3 applies.

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?

Specific verb pair plus resource: it processes ARCO rights requests and produces the official response model under the data-protection law. An agent immediately knows the domain object (solicitudes ARCO) and the deliverable. No sibling tool overlaps this function, so sibling differentiation is unnecessary but also absent.

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

Usage Guidelines2/5

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

There is no statement of when to invoke this versus alternatives, no prerequisites (e.g. a received request, a valid RUT, a legal deadline), and no note on what should happen after the model is generated. Usage is only inferable from the topic name and description.

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