Skip to main content
Glama

meskeIA MCP

by com.meskeia

calcular_inflacion

Read-only

Calcula el equivalente en poder adquisitivo de una cantidad monetaria entre dos años cualquiera de la historia de España (1961-2025). Usa el IPC histórico del INE (base 2021 = 100) para determinar: el valor equivalente en el año destino, la inflación acumulada en el período y la inflación media anual (CAGR). Útil para comparar salarios, precios o inversiones entre épocas diferentes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cantidadYesCantidad monetaria en euros (o pesetas históricas, el resultado será proporcional)
anoOrigenYesAño de la cantidad original (1961-2025)
anoDestinoYesAño al que se quiere convertir (1961-2025). Puede ser anterior al año origen para calcular hacia atrás.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only provide readOnlyHint=true. The description adds transparency by stating the data source (IPC histórico del INE base 2021=100) and the specific outputs (valor equivalente, inflación acumulada, inflación media anual). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is two sentences, efficiently front-loading purpose and methodology. Every sentence adds value without redundancy.

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?

Given full schema coverage and annotations indicating read-only, the description explains the outputs (equivalente, inflación acumulada, CAGR) and data source. No return value schema exists, but outputs are clearly described.

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% with already clear parameter descriptions. The description adds little beyond restating the year range and mentioning 'o pesetas históricas', which is implied. Baseline 3 is appropriate.

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 clearly states the tool calculates the purchasing power equivalent of a monetary amount between two years in Spain (1961-2025), specifying the verb, resource, and scope. It distinguishes itself from sibling calculator tools by focusing on inflation adjustment.

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?

The description provides context for when to use the tool ('Útil para comparar salarios, precios o inversiones entre épocas diferentes'), but does not explicitly exclude cases or compare with siblings. However, siblings are all distinct calculator tools, so no exclusion is necessary.

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

All meskeIA MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools are cleanly separated by domain and purpose, but a few close pairs exist: calcular_camara_lenta and calcular_regla_180_video both touch the 180° shutter rule, and calcular_pace_running and calcular_prediccion_running both produce race projections. The descriptions are detailed enough to resolve the ambiguity, but misselection is possible if they are not read carefully.

Naming Consistency5/5

All tool names follow a consistent Spanish verb_noun snake_case pattern, with calcular_ dominating and the other verbs (convertir_, consultar_, recomendar_, escalar_) used for genuinely different action types. There is no mixed casing or style inconsistency.

Tool Count2/5

42 tools is far above the 25+ threshold and the set spans many unrelated domains such as cooking, fitness, photography, vehicles, dates, and finance. While each individual calculator may be useful, the server is not well-scoped and would be much easier to navigate if split into domain-specific MCP servers.

Completeness3/5

Coverage inside each sub-domain is quite thorough, but there are notable gaps: calcular_kilometraje references calcular_irpf, calcular_cuota_autonomo, and comparar_autonomo_vs_sl, none of which exist in this server. These dangling cross-references can lead an agent to attempt calling unavailable tools.

Resources