Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Validar RUT/RUN (Chile)

cl-rut
Read-onlyIdempotent

Valida un RUT/RUN chileno con su dígito verificador mod 11 (0-9 o K) y lo formatea. Solo valida: el dígito debe venir incluido. Cuándo: hay que comprobar sin conexión un documento o número de cuenta de LatAm o España dado por un usuario antes de guardarlo o usarlo; la herramienta solo valida. No para: validar un CPF brasileño (br-cpf-validate). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Validates a Chilean RUT/RUN including its mod-11 check digit (0-9 or K) and returns it formatted as 12.345.678-5. Validation only: the check digit must be supplied and is never computed. When: a user-supplied Latin American or Spanish ID or account number has to be checked offline before it is stored or used; the tool only validates. Not for: validating a Brazilian CPF (br-cpf-validate). [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
rutYesRUT including check digit, e.g. 12.345.678-5 (string; required; up to 20 chars).

Output Schema

NameRequiredDescriptionDefault
validNo
reasonNo
formattedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / rut / examples
      Added value: +[
+  "12.345.678-5"
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Validates a Chilean RUT/RUN including its mod-11 check digit (0-9 or K) and returns it formatted as 12.345.678-5. Validation only: the check digit must be supplied and is never computed. When: a user-supplied Latin American or Spanish ID or account number has to be checked offline before it is stored or used; the tool only validates. Not for: validating a Brazilian CPF (br-cpf-validate). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, destructive=false and openWorldHint=false, so the safety profile is given. The description still earns credit by adding operational limits not present in annotations (64 KB input, 1 s per call, 1 MB result) and the key behavioral rule that the check digit is never computed and must be supplied 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and organized with explicit labels (Cuándo / No para / Efectos secundarios / Límites), so an agent can skim. The main waste is the full Spanish/English duplication of the same content within one description.

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?

Single required parameter, full schema description, an output schema (so return values need no explanation) and complete annotations. Nothing an agent needs in order to call this correctly is missing, and the limits section covers the remaining operational unknowns.

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% (type, maxLength 20, example), so the baseline is 3. The description adds genuinely non-schema semantics: the check digit must be included in the input and will not be calculated, which prevents a common misuse of check-digit tools.

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 and resource ('Valida un RUT/RUN chileno con su dígito verificador mod 11') plus the output shape (formatted 12.345.678-5). It also explicitly marks itself as validation-only, which distinguishes it from formatting/generation tools in the sibling list.

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?

Explicit 'Cuándo' section and an explicit exclusion naming the sibling br-cpf-validate, which is exactly the kind of routing an agent needs. However, the positive condition is phrased broadly ('a user-supplied Latin American or Spanish ID or account number'), which could tempt an agent to send an Argentine CUIT or Mexican CURP to a Chilean-only validator; only the Brazilian CPF is called out as an alternative.

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

All Burs-IA Utils toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources