Skip to main content
Glama

Repartir dinero sin perder centavos

money-allocate
Read-onlyIdempotent

Divide un monto en partes (por proporciones o iguales) en unidades menores, sin perder centavos: la suma siempre cuadra. Cuándo: un cálculo de dinero, impuestos o matemática financiera tiene que ser exacto y reproducible (redondeo, centavos, tasas). No para: dividir una cuenta entre personas con propina opcional y redondeo de cada parte (bill-split). 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: Splits an amount into parts by ratios or equally, in integer minor units using the largest-remainder method so the parts always add up exactly to the total. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: splitting a bill among people with an optional tip % (bill-split). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "parts": 3,
      "amount": 100
    },
    "name": "money-allocate"
  }
}

Input Schema

NameRequiredDescriptionDefault
partsNoEqual parts when no ratios (integer; optional; min 1; max 1000).
amountYesTotal amount (number; required; min 0; max 10000000000000).
ratiosNoRatios (e.g. [50, 30, 20]); omit with parts for equal split (array of number; optional; at least 1 items; up to 1000 items).
currencyNoISO 4217 currency code (string; optional; default "USD"; pattern ^[A-Za-z]{3}$).USD

Output Schema

NameRequiredDescriptionDefault
totalNo
allocationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "amount": 100,
      +    "parts": 3
      +  }
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / amount / examples
      Added value: +[
      +  100
      +]
  3. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Splits an amount into parts by ratios or equally, in integer minor units using the largest-remainder method so the parts always add up exactly to the total. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: splitting a bill among people with an optional tip % (bill-split). 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."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false, idempotentHint and destructiveHint=false, so the "sin red, sin estado guardado, determinista" clauses largely restate structured data. However, the description adds genuinely new behavior: the largest-remainder rounding method (explaining why the sum is exact) and hard limits of 64 KB input, 1 s per call and 1 MB result. That is real operational context an agent cannot get from the annotations.

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?

The Spanish block is tightly front-loaded with explicit labels (Cuándo, No para, Efectos secundarios, Determinista, Límites), so an agent can scan it quickly. The cost is the near-duplicate English rendering, which doubles length for little added information, keeping it short of a 5.

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?

With an output schema present, return values need no explanation, and the description still covers purpose, exclusivity versus bill-split, purity/determinism and concrete resource limits. Nothing an agent needs in order to call this 4-parameter tool correctly is missing.

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%, so the schema already documents parts, amount, ratios and currency, and the baseline of 3 applies. The description adds one meaningful clarification — that values are expressed in integer minor units — which the schema's "Total amount (number)" does not state, but it says nothing about how ratios interact with parts beyond what the schema already notes.

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 ("Divide un monto en partes") plus the exact mechanism (proporciones o iguales, unidades menores, largest-remainder) and the guarantee that the parts sum to the total. It also names the sibling it is not (bill-split), so an agent can separate it from that tool 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 routing: "Cuándo: un cálculo de dinero, impuestos o matemática financiera tiene que ser exacto y reproducible" and "No para: dividir una cuenta entre personas con propina opcional (bill-split)". Both the positive trigger and the negative exclusion are stated, which is the strongest form of guidance.

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