Skip to main content
Glama

meskeIA MCP

by com.meskeia

calcular_macros

Read-only

Calcula las necesidades calóricas diarias y la distribución óptima de macronutrientes. Usa la fórmula Mifflin-St Jeor para la TMB (Tasa Metabólica Basal) y multiplica por el factor de actividad para obtener el TDEE. Ajusta las calorías según el objetivo (definición -500 kcal, mantenimiento 0, volumen +400 kcal) y distribuye en proteínas, carbohidratos y grasas. ⚠️ Orientativo — consultar con dietista-nutricionista titulado para planes personalizados.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
edadYesEdad en años
pesoYesPeso corporal en kilogramos
sexoYesSexo biológico (determina la constante de la fórmula Mifflin-St Jeor)
alturaYesAltura en centímetros
objetivoYes"definicion" (déficit -500 kcal, 30P/40C/30G%), "mantenimiento" (0 kcal, 25P/50C/25G%), "volumen" (superávit +400 kcal, 25P/50C/25G%)
nivelActividadYes"sedentario" (sin ejercicio), "ligero" (1-3 días/semana), "moderado" (3-5 días), "activo" (6-7 días), "muy_activo" (ejercicio intenso diario o 2x/día)

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description adds detailed behavioral context: the formula used (Mifflin-St Jeor), multiplication by activity factor for TDEE, calorie adjustments for goals, and macronutrient distribution percentages. No contradiction with 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?

Description is concise (5 sentences), front-loaded with the primary purpose, and efficiently structured: purpose, method, adjustments, disclaimer. No extraneous information.

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?

Given 6 required parameters and no output schema, the description explains the entire calculation process thoroughly. However, it doesn't specify the output format (e.g., calories, grams of protein/carbs/fat), which slightly reduces completeness.

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% with precise descriptions for all 6 parameters. The description adds overall methodology but does not enhance parameter meaning beyond what the schema 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?

Description clearly states it calculates daily caloric needs and optimal macronutrient distribution using a specific formula (Mifflin-St Jeor), distinguishing it from sibling calculators like 'calcular_gasto_energetico' which focus only on energy expenditure.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like 'calcular_imc' or 'calcular_gasto_energetico'. The disclaimer about consulting a dietitian is a safety note, not usage context.

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