Skip to main content
Glama

meskeIA MCP

by com.meskeia

calcular_ganache

Read-only

Calcula las proporciones exactas de chocolate y nata para un ganache según el tipo de chocolate (negro extra/negro/semi-fondant/con leche/blanco) y la textura deseada (glaseado/trufa/firme). El ratio se ajusta automáticamente al porcentaje de cacao.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
texturaNoglaseado: fluido para tartas/eclairs | trufa: para bolear trufas y rellenar bombones | firme: muy denso para modelar. Por defecto trufa.
total_gNoGramos totales de ganache a preparar. Por defecto 200g.
tipo_chocolateNonegro_extra >70% | negro 55-70% | semi_fondant 40-55% | con_leche 28-40% | blanco 0% cacao. Por defecto negro.

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint annotation already signals no side effects. The description adds that the ratio adjusts automatically to cacao percentage, providing some behavioral context. However, it does not disclose default behaviors or output format beyond 'proporciones exactas'.

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 concise sentences that front-load the core purpose and immediately follow with the crucial automatic adjustment behavior. No redundant or extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple calculator with three parameters and no output schema, the description is adequate but could be slightly more complete by specifying the output format (e.g., 'proporciones en gramos') or clarifying the result type. Still, it covers the essential purpose and inputs.

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%, with each parameter already having detailed descriptions including defaults and cacao ranges. The tool description restates the parameter choices but adds minimal new meaning beyond summarizing the schema.

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 verb ('Calcula las proporciones exactas') and the resource (ganache). It specifies the input factors (chocolate type and texture) and distinguishes this tool from sibling calculators by being specific to ganache.

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?

The description implies usage for ganache proportion calculations via its specific input parameters, but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among the many sibling calculator tools.

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