Calcula el Índice de Masa Corporal (IMC) a partir del peso y la altura. Devuelve la categoría (normopeso, sobrepeso, obesidad...), el rango de peso saludable y cuántos kg faltan o sobran para alcanzarlo. ⚕️ Herramienta orientativa — no reemplaza valoración médica.
| Name | Required | Description | Default |
|---|---|---|---|
| pesoKg | Yes | Peso en kilogramos (ej: 75) | |
| alturaCm | Yes | Altura en centímetros (ej: 175) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description adds a disclaimer about medical use, reinforcing safe behavior. 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, no redundancy. Includes emoji for readability and disclaimer. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite lacking an output schema, the description mentions return values (category, healthy range, deviation). Sufficient for a simple calculation tool with read-only intent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema covers 100% of parameters with detailed descriptions and examples. The description adds minimal extra meaning beyond the schema (e.g., example values). Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it calculates BMI from weight and height, returns category and healthy range. The verb 'calcula' and resource 'Índice de Masa Corporal' are specific and distinct from sibling tools which cover different domains.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says it's orientative and does not replace medical evaluation, which guides appropriate use. However, it doesn't specify when to use versus alternative tools or exclude specific populations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.
