Burs-IA Utils

Calcular descuentos

discount-calculate

Read-onlyIdempotent

Aplica uno o varios descuentos (porcentaje o fijo), compuestos o sumados, y opcionalmente el impuesto después. Cuándo: un cálculo de dinero, impuestos o matemática financiera tiene que ser exacto y reproducible (redondeo, centavos, tasas). No para: calcular utilidad, margen bruto % (margin-markup). 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: Applies one or more percentage and fixed discounts to a price, either compounded in order or summed, optionally adding tax afterwards; reports effective discount %. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: computing profit, gross margin % (margin-markup). 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.

Input Schema

Name	Required	Description	Default
`mode`	No	How to combine (optional; one of: compound, additive; default "compound").	compound
`price`	Yes	Original price (number; required; min 0; max 1000000000000000).
`decimals`	No	Decimals (integer; optional; default 2; min 0; max 6).
`discounts`	Yes	Discounts (array of object; required; at least 1 items; up to 20 items).
`tax_percent`	No	Tax % applied after discounts (number; optional; default 0; min 0; max 100).

Output Schema

Name	Required	Description	Default
`savings`	No
`final_price`	No
`price_with_tax`	No
`effective_discount_percent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / discounts / examples
```
Added value: +[
+  [
+    {
+      "percent": 20
+    },
+    {
+      "percent": 10
+    }
+  ]
+]
```
- addedInput schema / properties / price / examples
```
Added value: +[
+  100
+]
```
First observedNov 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so 'no side effects, read-only, no network, no stored state' largely restates structured data. However, the description adds genuinely new behavioral facts not in annotations: hard limits of 64 KB input, 1 s per call, 1 MB result, which matter for an agent planning a large discount array. Determinism claim is redundant with idempotentHint but harmless.

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 purpose and organized under labeled sections (When / Not for / Side effects / Limits), each carrying distinct information. The full ES+EN duplication doubles the length without adding information, which is the main cost; the individual sentences themselves are tight.

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. With usage conditions, exclusions, side-effect profile, determinism and execution limits all covered, an agent has everything needed to decide to call it and to size its input correctly.

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 baseline is 3, but the description adds real meaning the schema lacks: the mode values translate to 'compounded in order' vs 'summed', revealing that ordering matters, and it clarifies tax is applied after discounts and that the output reports the effective discount %. It does not, however, clarify how a mixed percent/amount discount object is resolved.

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 (applies one or more percentage/fixed discounts), the two combination modes, that tax is applied afterwards, and that it reports an effective discount %. Explicitly names the sibling it is not for (margin-markup), so the agent can distinguish it without opening either 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?

Has explicit 'When' (money/tax/financial math needing exact, reproducible results with rounding and cents) and 'No para / Not for' (profit, gross margin % → margin-markup) clauses in both languages. The condition that selects the alternative tool is spelled out, not inferred.

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?