Skip to main content
Glama

meskeIA MCP

by com.meskeia

calcular_zonas_cardiacas

Read-only

Calcula las 5 zonas de frecuencia cardíaca personalizadas con la fórmula de Karvonen. Más precisa que el simple % FCmáx porque tiene en cuenta la FC en reposo. Devuelve los rangos de pulsaciones para cada zona y su beneficio de entrenamiento.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
edadYesEdad en años
fc_maximaNoFCmáx medida en un test de esfuerzo en ppm. Opcional: si no se indica, se estima con 220−edad
fc_reposoYesFrecuencia cardíaca en reposo en ppm (medida por la mañana antes de levantarse)

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, indicating safety. The description adds value by detailing the formula (Karvonen), the reason for accuracy (resting HR), and the output (ranges per zone and training benefit), enhancing transparency beyond annotations.

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 with no wasted words. The first sentence states the action and method, the second explains the advantage and output. It is front-loaded and every sentence earns its place.

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 tool has moderate complexity (3 parameters, formula). No output schema, but the description states it returns 'los rangos de pulsaciones para cada zona y su beneficio de entrenamiento,' which adequately covers return values. Annotations provide readOnlyHint. No critical information 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 all three parameters. The description does not add new parameter-specific details beyond the schema's existing descriptions, meeting the baseline of 3.

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 specifies the tool calculates the 5 customized heart rate zones using the Karvonen formula, which is more accurate than simple max heart rate percentage. This clearly distinguishes it from sibling calculator tools, as none are dedicated to heart rate zones.

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 explains why to use this tool over simpler methods ('Más precisa que el simple % FCmáx porque tiene en cuenta la FC en reposo'), providing clear context for when it is appropriate. However, it does not explicitly state when not to use it or mention alternatives.

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