Datos UY/AR

Validar RUT uruguayo

uy_rut

Valida formato y dígito verificador de un RUT uruguayo (12 dígitos). No consulta a DGI: no confirma existencia ni vigencia.

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": {
      "rut": "<rut>"
    },
    "name": "uy_rut"
  }
}

Input Schema

Name	Required	Description	Default
`rut`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a critical limitation — it explicitly says it does NOT query DGI and does NOT confirm existence or vigencia, preventing an agent from over-trusting the result. It stops short of describing the return value shape (no output schema exists), so the transparency is useful but not complete.

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?

Two short sentences, the capability is front-loaded and the limitation follows immediately. No filler.

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?

For a one-parameter validator with no annotations and no output schema, the description covers scope and the key negative guarantee, but leaves real gaps: the exact accepted input format and what the tool returns on success or failure.

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 0% — the single 'rut' parameter has no description, only min/max length. The description partially compensates by stating the expected format (12 digits), but this conflicts with the schema's maxLength of 32, leaving the accepted input format (separators, hyphens) ambiguous.

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 plus the exact scope: validates format and check digit of a Uruguayan RUT. No sibling in the list (feriados, cotizaciones, ui) does anything comparable, so no differentiation is needed.

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 (call it to validate a RUT) but there is no explicit when-to-use, when-not-to-use, or named alternative. The scope disclaimer 'no consulta a DGI' borders on guidance but describes behavior rather than when to pick this tool.

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

All Datos UY/AR tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?