Burs-IA Utils

Aritmética de enteros grandes

bigint-calc

Read-onlyIdempotent

Realiza aritmética exacta de enteros grandes: suma, resta, multiplicación, división, potencia, comparación. Cuándo: un resultado numérico tiene que ser exacto o reproducible y no estimado. No para: evaluar una expresión matemática con un analizador propio (expression-evaluate). 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: Computes the exact arbitrary-precision integer arithmetic: add, subtract, multiply, divide (floor quotient and remainder), power (result ≤ 10,000 digits), compare. When: a numeric result has to be exact or reproducible instead of estimated. Not for: evaluating an arithmetic expression with its own parser (expression-evaluate). 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
`a`	Yes	First integer (integer or string; required; up to 5001 chars; pattern ^-?\d{1,5000}$).
`b`	Yes	Second integer (integer or string; required; up to 5001 chars; pattern ^-?\d{1,5000}$).
`operation`	Yes	Operation (required; one of: add, subtract, multiply, divide, power, compare).

Output Schema

Name	Required	Description
`result`	No	any JSON value
`quotient`	No
`remainder`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026
- addedInput schema / properties / a / examples
```
Added value: +[
+  "99999999999999999999"
+]
```
- addedInput schema / properties / b / examples
```
Added value: +[
+  "1"
+]
```
- addedInput schema / properties / operation / examples
```
Added value: +[
+  "add"
+]
```
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 goes further by adding operational limits (64 KB input, 1 s per call, 1 MB result), the power digit cap (≤10,000 digits), and a determinism guarantee. These are concrete constraints an agent cannot infer from the annotations or schema.

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?

Content is front-loaded with purpose, then when/not-for, then side effects and limits — a logical order with no filler sentences. However, the entire block is duplicated in Spanish and English, which roughly doubles length for identical 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. With limits, determinism, side-effect disclosure, sibling routing, and 100% param coverage 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%, establishing a baseline of 3, but the description adds real semantic value: it clarifies that 'divide' returns floor quotient and remainder, and that power results are bounded at 10,000 digits. The a/b/operation parameters themselves are not elaborated beyond the schema, so not a full 5.

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 ('Realiza aritmética exacta de enteros grandes') and enumerates the supported operations (add, subtract, multiply, divide, power, compare). It explicitly names the sibling it is not (expression-evaluate), so an agent can distinguish it without opening schemas.

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?

Provides an explicit 'When:' condition (result must be exact/reproducible, not estimated) and an explicit 'Not for:' exclusion pointing to expression-evaluate. Both the selection and deselection criteria are stated outright.

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?