Skip to main content
Glama

meskeIA MCP

by com.meskeia

calcular_hidratacion_pan

Read-only

Calcula la hidratación de una masa de pan o los gramos de agua necesarios para una hidratación objetivo. Bidireccional: agua→% o %→agua. Clasifica la hidratación y da ejemplos de panes típicos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modoNocalcular_porcentaje: da harina_g + agua_g → devuelve %. calcular_agua: da harina_g + hidratacion_pct → devuelve gramos de agua. Por defecto calcular_porcentaje.
agua_gNoGramos de agua. Requerido si modo=calcular_porcentaje.
harina_gYesPeso de la harina en gramos.
hidratacion_pctNoPorcentaje de hidratación objetivo. Requerido si modo=calcular_agua.

TDQS

A4/5.0
Behavior4/5

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

Annotations provide readOnlyHint=true, already indicating safe read operation. Description adds value by disclosing bidirectional behavior (agua→% or %→agua) and that it classifies hydration and provides example breads. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences efficiently cover core functionality and additional features (bidirectional, classification, examples). Front-loaded with main purpose, no redundant words.

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?

Given no output schema, description provides sufficient context: what inputs are needed, what output to expect (hydration percentage or water grams), plus classification and examples. Lacks specifics on classification thresholds or error handling, but adequate for a simple calculator tool.

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 coverage is 100%, so baseline is 3. Description mentions bidirectional modes, which aligns with the 'modo' parameter's enum descriptions. Does not add novel semantics beyond what schema already provides for each parameter.

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?

Description clearly states it calculates bread dough hydration, either from water to percentage or percentage to water. Uses specific verb 'Calcula' and resource 'hidratación de pan'. Distinguishes from sibling 'calcular_porcentaje_panadero' by focusing on bread hydration and bidirectional functionality.

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?

Description implies usage for bread hydration calculations (e.g., when adjusting water or flour), but does not explicitly state when to avoid or recommend alternatives. No direct comparison to related siblings like 'calcular_porcentaje_panadero'. Context is clear but lacks explicit guidance.

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