Skip to main content
Glama

meskeIA MCP

by com.meskeia

recomendar_vehiculo

Read-only

Recomienda el segmento (urbano, compacto, SUV, familiar) y la motorización (gasolina, diésel, híbrido, eléctrico) más adecuados según el perfil del usuario. Necesita al menos los km anuales. Opcionales: uso principal, pasajeros, presupuesto, zona y si hay ZBE. Devuelve segmento recomendado, motorización, razón principal, coste anual estimado y alertas contextuales.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zbeNotrue si la ciudad tiene Zona de Bajas Emisiones activa (Madrid, Barcelona, Valencia...). Por defecto: false
zonaNoZona principal de uso del vehículo. Por defecto: ciudad
cargaNoNecesidad de maletero: poca/normal/mucha. Por defecto: normal
kmAnualesYesKilómetros que conduce al año (ej: 15000)
pasajerosNoNúmero habitual de ocupantes incluyendo el conductor. Por defecto: 4
presupuestoNoPresupuesto disponible para la compra. Por defecto: 15k_25k
usoPrincipalNourbano = mayoría en ciudad | mixto = ciudad+carretera | carretera = mayoría autopista. Por defecto: mixto

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds return fields (segment, motorization, reason, cost, alerts). No side effects or limitations are disclosed, but the tool's behavior is sufficiently transparent.

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?

The description is a single paragraph, front-loaded with main purpose, and efficiently covers inputs and outputs without unnecessary 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 the 7 parameters and no output schema, the description adequately explains inputs and outputs. However, it could provide more detail on output format or edge cases for full completeness.

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

Parameters5/5

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

Schema coverage is 100% with good parameter descriptions. The description adds value by listing required vs. optional parameters and summarizing return fields, exceeding what schema provides.

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 tool recommends vehicle segment and motorization based on user profile, specifying required and optional parameters. It is distinct from sibling tools which are calculation- or conversion-oriented.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for vehicle recommendation but does not explicitly contrast with sibling tools or state when to avoid use. Context is clear but not explicit about alternatives.

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