Burs-IA Utils

Valor en letras para cheques (Colombia)

co-amount-in-words

Read-onlyIdempotent

Escribe un valor en pesos en letras como en cheques, facturas y contratos colombianos ("UN MILLÓN DOSCIENTOS MIL PESOS M/CTE"). Cuándo: hay que aplicar con exactitud una regla colombiana (DIAN, festivos de la Ley Emiliani, montos en COP, IVA, GMF, UVT), p. ej. al facturar o cobrar. No para: escribir un entero hasta 10^18 en palabras en español (es-number-to-words). 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: Writes a peso amount in words in the format used on Colombian cheques, invoices and contracts, e.g. "UN MILLÓN DOSCIENTOS MIL PESOS M/CTE", with cents as fraction (50/100) or words. When: a Colombian rule (DIAN, Ley Emiliani holidays, COP amounts, IVA, GMF, UVT) has to be applied exactly, e.g. in invoicing or payment flows. [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`amount`	Yes	Amount as number or decimal string (up to 2 decimals) (number or string; required; up to 30 chars).
`suffix`	No	Suffix (string; optional; default "M/CTE"; up to 20 chars).	M/CTE
`uppercase`	No	Uppercase (boolean; optional; default true).
`cents_style`	No	Cents (optional; one of: fraction, words, omit_if_zero; default "omit_if_zero").	omit_if_zero

Output Schema

Name	Required	Description	Default
`words`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / amount / examples
```
Added value: +[
+  1200000
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Writes a peso amount in words in the format used on Colombian cheques, invoices and contracts, e.g. \"UN MILLÓN DOSCIENTOS MIL PESOS M/CTE\", with cents as fraction (50/100) or words. When: a Colombian rule (DIAN, Ley Emiliani holidays, COP amounts, IVA, GMF, UVT) has to be applied exactly, e.g. in invoicing or payment flows. Not for: spelling an integer up to 10^18 in Spanish words (es-number-to-words). 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.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description still adds non-duplicative context: no network, no stored state, determinism, and concrete limits (64 KB JSON input, 1 s per call, 1 MB result). That latency/size envelope is exactly the kind of operational detail annotations cannot express.

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 purpose, then When / Not for / Side effects / Determinism / Limits in a scannable order, and the closing pointer to the full EN version avoids bloat. The cost is a near-complete Spanish/English duplication, which inflates the block without adding information.

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, so return values need no prose; what remains — scope, exact-rule trigger, alternative tool, purity, determinism, and size/time limits — is all present. Nothing an agent needs to call this correctly is missing.

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%, so the baseline is 3; the description earns a bump by clarifying the cents representation ("fraction (50/100) or words"), which gives real meaning to the cents_style enum, and its example fixes the suffix convention "M/CTE". It still leaves uppercase and the amount string-vs-number handling to the schema.

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 (write a peso amount in words in Colombian cheque/invoice format) and anchors it with a literal output example "UN MILLÓN DOSCIENTOS MIL PESOS M/CTE". It explicitly separates itself from es-number-to-words, so the agent can pick correctly among the many number/word siblings 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" / "No para" structure: use when an exact Colombian rule (DIAN, Ley Emiliani, COP, IVA, GMF, UVT) applies, e.g. invoicing or payment flows; do not use for spelling a plain integer in Spanish (es-number-to-words). Both the positive trigger and the exclusion name a concrete 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 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?