Calcula cuánto tiempo hay entre dos fechas: días totales, semanas, meses y desglose exacto en años/meses/días. Útil para plazos, antigüedad, tiempo transcurrido o tiempo restante hasta un evento.
| Name | Required | Description | Default |
|---|---|---|---|
| fechaFin | Yes | Fecha final en formato YYYY-MM-DD o "hoy" | |
| fechaInicio | Yes | Fecha inicial en formato YYYY-MM-DD o "hoy" |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the types of outputs (days, weeks, months, years/months/days) and mentions the 'hoy' input option. Annotations already indicate readOnlyHint=true, so the description adds value by specifying the calculation scope and input flexibility.
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 efficiently convey purpose, output details, and use cases. No extraneous text; 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 no output schema, the description fully explains what the tool returns (days, weeks, months, exact breakdown). It covers input format and 'hoy' special value. All necessary information is present.
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?
Schema coverage is 100% with clear descriptions for both parameters (fechaInicio, fechaFin). The description does not add meaning beyond what the schema already provides; it only restates the concept of two dates.
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 time difference between two dates, listing specific outputs (days, weeks, months, exact breakdown). It distinguishes itself from sibling tools like 'calcular_edad' and 'calcular_dia_semana' by focusing on date ranges.
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 provides context on when to use the tool: 'Útil para plazos, antigüedad, tiempo transcurrido o tiempo restante hasta un evento.' It does not explicitly exclude cases or name alternatives, but the use cases are clear and relevant.
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.
