Skip to main content
Glama

meskeIA MCP

by com.meskeia

calcular_estadisticas

Read-only

Calcula los principales descriptores estadísticos de un conjunto de datos numéricos: media, mediana, moda, varianza, desviación típica, percentiles (Q1/Q2/Q3), rango intercuartílico, coeficiente de variación y asimetría de Fisher. Muy útil para analizar rendimientos de inversiones, precios, gastos, ingresos, etc. Encadenable con cualquier tool que devuelva series de valores numéricos. Ideal para: "Analiza estas rentabilidades mensuales de mi cartera: [2.3, -1.1, 3.4, ...]"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nombreNoNombre descriptivo del conjunto de datos (ej: "Rendimientos cartera 2024").
valoresYesLista de valores numéricos a analizar (mínimo 2, máximo 1.000). Ejemplos: rendimientos mensuales, precios, gastos.
decimalesNoNúmero de decimales para los resultados. Por defecto 4.

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, so the description does not need to state safety. It adds behavioral context by listing exactly which statistics will be computed. However, it does not mention any permissions, rate limits, or edge cases (e.g., behavior with NaN or extreme values).

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 description is a single paragraph that front-loads the core purpose and lists statistics, followed by usage examples. It is efficient and avoids redundancy, though it could be slightly more structured (e.g., bullet points for statistics).

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?

The description covers the tool's purpose, output statistics, usage scenarios, and chainability. With no output schema, listing the computed statistics is sufficient. The description is complete for this tool's complexity and rich annotations.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning to parameters beyond the schema; it reiterates that 'valores' is a list of numbers but does not provide extra syntax or formatting details.

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 principal statistical descriptors of numerical datasets, listing many specific metrics (media, mediana, etc.). It distinguishes from sibling calculators by focusing on statistical analysis of numerical data, as opposed to other 'calcular_' tools for specific domains.

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 explicit usage context: useful for analyzing returns, prices, expenses, and chainable with any tool returning numerical series. It includes an example query. However, it does not explicitly state when NOT to use it or mention alternatives among siblings.

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