Skip to main content
Glama

Aurio Calculators

¿Me lo puedo permitir?

me_lo_puedo_permitir
Read-onlyIdempotent

Dice si te puedes permitir una compra sin romper tu colchón de emergencia, o cuántos meses tendrías que ahorrar. Úsala para “me puedo permitir un coche”, “me lo puedo permitir”, “puedo comprarme un iPhone”, “me da para irme de viaje”. English: “can I afford it?” check against savings and an emergency fund.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "precio": "<precio>",
      "ingresosMensuales": "<ingresosMensuales>",
      "gastosMensuales": "<gastosMensuales>",
      "ahorroActual": "<ahorroActual>"
    },
    "name": "me_lo_puedo_permitir"
  }
}

Input Schema

NameRequiredDescriptionDefault
precioYesPrecio de la compra en euros (coche, viaje, móvil…). Purchase price in EUR.
ahorroActualYesAhorro o liquidez disponible hoy en euros. Current savings in EUR.
mesesColchonNoMeses de gastos a conservar como colchón de emergencia (por defecto 3). Emergency fund months.
gastosMensualesYesGastos al mes en euros, incluidos los fijos. Monthly expenses in EUR.
ingresosMensualesYesIngresos netos al mes en euros. Monthly net income in EUR.

Output Schema

NameRequiredDescriptionDefault
ctaYes
kindYes
faltanYes
precioYes
veredictoYes
disclaimerYes
netoMensualYes
progresoPctYes
mesesColchonYes
veredictoTextoYes
ahorroTrasCompraYes
colchonEmergenciaYes
mesesParaPermitirteloYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context the annotations don't: the calculation is anchored on an emergency fund of monthly expenses and can return either a verdict or a savings timeline. It doesn't mention the default cushion length or any input constraints, but the output schema covers result shape.

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 outcome, then example trigger phrases, then an English gloss. The keyword list earns its place by aiding intent matching, though the near-duplicate Spanish phrasings ('me lo puedo permitir' vs 'me puedo permitir') are slightly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full parameter documentation, the description needs only to explain purpose and inputs at a high level, which it does. It could add one clause about the default 3-month cushion or how the monthly savings rate is derived, but nothing essential for correct invocation 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% and every parameter carries a bilingual description with units and ranges, so the schema does the heavy lifting. The description's only added semantic is the emergency-fund concept, which loosely maps to mesesColchon but adds no new detail beyond the schema's own default note.

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?

The description states a specific verb and outcome: it tells you whether you can afford a purchase without breaking your emergency cushion, or how many months you'd need to save. The bundled example phrasings (car, iPhone, trip) pin down the scope sharply enough to separate it from siblings like simular_ahorro or simular_hipoteca.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Trigger conditions are given as concrete user utterances ('me puedo permitir un coche', 'puedo comprarme un iPhone', 'can I afford it?'), which is strong positive guidance for routing. It stops short of saying when NOT to use it or naming an alternative tool for a different kind of check, so it falls short of a 5.

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