Skip to main content
Glama

meskeIA MCP

by com.meskeia

calcular_sustitucion_gelatina

Read-only

Convierte entre tipos de gelatina según el bloom strength: hojas de bronce (120), plata (160), oro (200, estándar europeo), platino (250), gelatina en polvo 200/250 bloom y agar-agar. Devuelve la tabla completa de equivalencias en gramos y hojas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unidadNoUnidad de medida. hojas solo aplica para tipos hoja_*. Por defecto gramos.
cantidadYesCantidad a convertir (en gramos u hojas según la unidad).
tipo_origenYesTipo de gelatina que tienes o que indica la receta. hoja_oro es la más común en supermercados.

TDQS

A3.9/5.0
Behavior4/5

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

The annotation readOnlyHint=true already indicates a safe read operation. The description adds behavioral detail by stating it returns 'la tabla completa de equivalencias en gramos y hojas', which informs the agent about the output format. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single sentence that front-loads the purpose with 'Convierte entre tipos de gelatina'. It lists all types efficiently but could be slightly improved by splitting into two sentences for readability. Overall concise and no wasted 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, the description explains what the tool returns ('la tabla completa de equivalencias en gramos y hojas'), which provides sufficient context for the agent to understand the result. It covers the core functionality without missing critical details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers all parameters with descriptions, but the description adds value by explaining the bloom strengths for each type (e.g., 'hojas de bronce (120), plata (160), ...'), which helps the agent understand the meaning behind the enum values. This context goes beyond 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 'convierte' (converts) and the resource 'tipos de gelatina según el bloom strength', listing all supported gelatin types. It distinguishes from sibling tools like 'convertir_unidades' by focusing specifically on gelatin substitution.

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?

The description does not provide guidance on when to use this tool versus alternatives. There is no mention of when to use this tool for gelatin conversions versus using 'convertir_unidades' or other sibling calculators, leaving the agent without clear usage context.

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