Skip to main content
Glama

Aritmética modular

modular-arithmetic
Read-onlyIdempotent

Calcula base^exponente mod m y el inverso modular cuando existe. Cuándo: un resultado numérico tiene que ser exacto o reproducible y no estimado. No para: realizar aritmética exacta de enteros grandes (bigint-calc). 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 base^exponent mod m (fast exponentiation) and, when it exists, the modular inverse of base mod m. Arbitrary precision up to 300 digits. When: a numeric result has to be exact or reproducible instead of estimated. Not for: computing the exact arbitrary-precision integer arithmetic (bigint-calc). 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

NameRequiredDescriptionDefault
baseYesBase (integer or string; required; up to 301 chars; pattern ^-?\d{1,300}$).
modulusYesModulus ≥ 1 (integer or string; required; up to 301 chars; pattern ^-?\d{1,300}$).
exponentNoExponent ≥ 0 (integer or string; optional; up to 301 chars; pattern ^-?\d{1,300}$).

Output Schema

NameRequiredDescriptionDefault
inverseNo
power_modNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / base / examples
      Added value: +[
      +  4
      +]
    • addedInput schema / properties / modulus / examples
      Added value: +[
      +  497
      +]
  2. First observed

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 the safety profile is covered. The description adds genuinely new context: determinism, 300-digit arbitrary precision, and concrete limits (64 KB input, 1 s per call, 1 MB result). The 'no network, no stored state' phrase partly restates annotations, keeping it just below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core computation, then labeled sections (When / Not for / Side effects / Deterministic / Limits) that are easy to scan. The bilingual duplication makes it longer than strictly necessary, but each labeled line carries distinct 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 not be explained. Combined with annotations covering safety and the description covering precision, determinism and resource limits, an agent has everything needed to call it 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 the baseline is 3. The description adds meaning beyond the schema: the 300-digit precision bound and the condition that the inverse is returned only 'when it exists' (i.e. base coprime to modulus), which the schema does not state.

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: computes base^exponent mod m and the modular inverse when it exists. It also names the sibling it is not (bigint-calc), so an 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?

Explicit 'When' clause (exact/reproducible numeric result instead of estimated) and an explicit 'Not for' clause routing arbitrary-precision integer arithmetic to bigint-calc. Both the positive and negative conditions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources