Skip to main content
Glama

meskeIA MCP

by com.meskeia

calcular_swolf_natacion

Read-only

Calcula el índice SWOLF (segundos + brazadas por largo) como medida de eficiencia en natación. Clasifica el nivel del nadador y proporciona consejo de mejora técnica. Compatible con piscinas de 25m y 50m.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metros_largoNoLongitud del largo en metros: 25 (defecto) o 50
brazadas_largoYesNúmero de brazadas por largo
tiempo_s_largoYesTiempo por largo en segundos (ej. 20 para nadar 25m en 20 segundos)

TDQS

A4.2/5.0
Behavior4/5

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

The description adds behavioral context beyond the readOnlyHint annotation: it states that the tool classifies level and provides advice, which are outputs. It does not contradict the annotation (readOnlyHint=true implies no side effects, consistent). No additional behavioral details needed.

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?

Three efficient sentences: defines SWOLF, states outputs (classification, advice), and notes pool lengths. No filler; front-loaded with core purpose. 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 description covers inputs and outputs adequately for a calculator, but does not specify the classification scale or detail of advice. However, given no output schema, this is a minor gap. It is almost complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. The description adds value by explaining what SWOLF means (segundos + brazadas por largo) and mentioning compatibility with 25m and 50m pools, which clarifies the metros_largo parameter. This exceeds the schema's descriptions.

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 SWOLF index, classifies swimmer level, and provides improvement advice. It is specific about verb (calcula) and resource (índice SWOLF and nivel del nadador), and it is distinct from sibling tools which are unrelated domains.

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

Usage Guidelines3/5

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

No explicit guidance on when to use or alternatives. The usage is implied by the domain (swimming efficiency), but the description does not include exclusions or comparison with other tools, so it relies on 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