meskeIA MCP

calcular_camara_lenta

Read-only

Calcula el factor de ralentización de un vídeo slow motion a partir de los fps de grabación y reproducción. Devuelve el multiplicador (ej. 4×), el obturador correcto según la regla 180° y la duración del clip ralentizado.

Input Schema

TableJSON Schema

Name	Required	Description
`fps_grabacion`	Yes	FPS a los que se graba (ej. 60, 120, 240, 960)
`fps_reproduccion`	Yes	FPS a los que se reproducirá (ej. 24, 25, 30)
`duracion_grabacion_s`	No	Duración del clip grabado en segundos. Opcional: si se indica, calcula la duración ralentizada

TDQS

A3.6/5.0

Behavior4/5

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

The description accurately describes a read-only calculation (consistent with readOnlyHint annotation) and discloses the 180° shutter rule. No hidden behaviors or side effects are implied. It adds context beyond annotations by mentioning the specific calculation method.

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 extraneous words. It front-loads the core purpose and immediately lists outputs. Every sentence serves a purpose.

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?

For a simple calculation tool with 3 parameters (all documented) and no output schema, the description sufficiently covers what the agent needs: inputs, calculation, and outputs. It lacks details on error handling or edge cases, but these are not critical for a deterministic calculator.

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 baseline is 3. The description adds minimal extra meaning: it confirms duration is used to compute final clip length, but this is already implied by the schema description. No deeper semantics are added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool computes a slow-motion factor from recording and playback fps, listing outputs (multiplier, shutter, duration). It is specific and useful, but does not explicitly differentiate from sibling calculators like 'calcular_regla_180_video', which might offer overlapping functionality.

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 guidance is provided on when to use this tool versus alternatives. The description only states what it does, without indicating context, prerequisites, or exclusion criteria. Given many sibling calculator tools, this omission leaves the agent without decision support.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All meskeIA MCP tools Inspect

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

Need Help?