Skip to main content
Glama

meskeIA MCP

by com.meskeia

calcular_porcentaje

Read-only

Realiza cálculos con porcentajes. Cinco modos disponibles: (1) percentOf: ¿cuánto es el X% de Y?, (2) whatPercent: ¿qué % es X de Y?, (3) increase: aumentar X en Y%, (4) decrease: disminuir X en Y%, (5) variation: variación porcentual de X a Y.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modoYesTipo de cálculo: percentOf = ¿cuánto es el X% de Y?, whatPercent = ¿qué % es X de Y?, increase = aumentar X en Y%, decrease = disminuir X en Y%, variation = variación porcentual de X a Y
valor1YesPrimer valor. Según el modo: percentOf → porcentaje (ej: 15 para 15%), whatPercent → cantidad parcial, increase/decrease → valor inicial, variation → valor inicial
valor2YesSegundo valor. Según el modo: percentOf → cantidad base, whatPercent → cantidad total, increase/decrease → porcentaje a aplicar, variation → valor final

TDQS

A3.8/5.0
Behavior3/5

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

The description accurately indicates the tool performs calculations, consistent with the readOnlyHint annotation. It adds minimal behavioral context beyond the annotation, but there is no contradiction.

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

Conciseness3/5

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

The description is a single sentence that conveys the purpose and modes, but it is somewhat lengthy (65 words). It could be more concise or structured (e.g., using bullet points) for easier scanning.

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?

For a calculation tool with three parameters and no output schema, the description adequately explains all modes and parameter roles. No critical information 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?

The input schema covers 100% of parameters with descriptions. The tool description restates the modes but does not add additional semantic meaning beyond what the schema already provides. 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 performs percentage calculations with five distinct modes, each briefly explained. It effectively distinguishes from sibling tools (other calculators) by specifying its unique functionality.

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 lists five modes and their use cases, providing clear guidance on when to use each. However, it lacks explicit instructions on when not to use this tool or comparisons to alternatives, which would make it more comprehensive.

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