Calcula la velocidad de obturación correcta para vídeo según la regla de los 180°. El obturador debe ser el doble del frame rate para conseguir motion blur natural. Devuelve el obturador recomendado y una tabla con todos los fps comunes.
| Name | Required | Description | Default |
|---|---|---|---|
| fps | Yes | Frame rate de grabación (ej. 24, 25, 30, 50, 60, 120, 240) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description fully discloses the output ('obturador recomendado y una tabla') and the rule used. Annotations declare readOnlyHint=true, and the description aligns, indicating no destructive effects. 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?
Two sentences that efficiently state purpose, the rule, and the output. No redundant or extraneous information. Ideal length for quick comprehension.
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?
The tool is simple with one parameter and no output schema. The description adequately covers what it does, the rule, and what it returns. No gaps given the low complexity.
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?
The single parameter (fps) has high schema coverage (100%), and the description adds value by explaining the 180-degree rule rationale ('el obturador debe ser el doble del frame rate'), enriching understanding beyond the schema's basic description.
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 the tool calculates the correct shutter speed for video based on the 180-degree rule, which directly differentiates it from sibling tools like calcular_camara_lenta (slow motion calculations) and calcular_filtro_nd_video (ND filter calculations). The verb 'calcula' and specific resource 'velocidad de obturación' make the purpose unambiguous.
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?
The description explains the tool's function but does not explicitly state when to use it versus alternatives (e.g., when to use this instead of calcular_camara_lenta). The context is clear but lacks exclusionary guidance, so it scores at the 'implied usage' level.
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.
