Burs-IA Utils

Validar CUIT/CUIL (Argentina)

ar-cuit-validate

Read-onlyIdempotent

Valida un CUIT/CUIL argentino (11 dígitos, dígito verificador mod 11) e identifica el tipo de prefijo. 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 una CBU/CVU argentina de 22 dígitos (ar-cbu-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 an Argentine CUIT/CUIL (11 digits: type prefix, DNI, mod-11 check digit with weights 5432765432) and identifies the prefix type (person or company). 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 22-digit Argentine CBU/CVU (ar-cbu-validate). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`cuit`	Yes	CUIT/CUIL (string; required; up to 20 chars).

Output Schema

Name	Required	Description	Default
`valid`	No
`reason`	No
`formatted`	No
`prefix_type`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / cuit / examples
```
Added value: +[
+  "33-69345023-9"
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Validates an Argentine CUIT/CUIL (11 digits: type prefix, DNI, mod-11 check digit with weights 5432765432) and identifies the prefix type (person or company). 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 22-digit Argentine CBU/CVU (ar-cbu-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."

First observedNov 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already carry readOnly/idempotent/openWorld/destructive hints, so the bar is lower; the description nonetheless adds useful operational detail (no network, no stored state, deterministic output, 64 KB input / 1 s / 1 MB limits). Some of the safety wording restates what the annotations declare, keeping it just short of a 5.

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?

Front-loaded with what the tool does, then when/not-for/effects/limits, one line each. The bilingual duplication with a pointer to the schema's EN text is slightly redundant but compact and well-structured.

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?

An output schema exists, annotations cover safety, and the description fills the remaining gaps an agent needs: determinism, offline behavior, size/time limits, and the sibling it must not be confused with. Nothing material is missing for a single-param validator.

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 the single 'cuit' parameter is documented with type, length and an example. The description adds algorithm context (weights 5432765432) rather than input-format guidance, so it adds little 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 and resource with technical specificity (11 digits, prefix type, mod-11 check digit with weights) and explicitly differentiates from the sibling ar-cbu-validate (22-digit CBU/CVU). An agent can select this over near neighbors without opening a schema.

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

Usage Guidelines5/5

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

Uses explicit 'Cuándo/When' and 'No para/Not for' sections, naming the exact alternative tool (ar-cbu-validate) and the condition that selects it. It also gives the concrete context (offline pre-storage check of user-supplied IDs).

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 tools Inspect

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

Need Help?