Skip to main content
Glama

meskeIA MCP

by com.meskeia

consultar_etiqueta_dgt

Read-only

Calcula la etiqueta medioambiental DGT (CERO, ECO, C, B o Sin etiqueta) de un vehículo según su combustible y año de matriculación. También informa del acceso a las Zonas de Bajas Emisiones (ZBE) de Madrid, Barcelona, Valencia, Sevilla, Zaragoza, Valladolid y Bilbao. Encadenable con recomendar_vehiculo para completar el perfil de un vehículo en consideración.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
combustibleYeselectrico = BEV | phev = híbrido enchufable | hibrido = híbrido convencional HEV | gnc_glp = gas natural/propano | gasolina | diesel
autonomiaPhevKmNoSolo para PHEV: autonomía eléctrica en km. ≥40km → etiqueta CERO, <40km → ECO. Por defecto: 0
anioMatriculacionYesAño de primera matriculación del vehículo (ej: 2018)

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the burden is lower. Description adds context about ZBE access but does not disclose limitations or data sources. No contradiction.

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, front-loaded with the core purpose, then additional outputs and chaining tip. Every sentence adds value; no wasted words.

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?

No output schema exists, so description should clarify what the tool returns. It mentions 'informa del acceso a las ZBE' but not the format (e.g., string, object). Missing edge cases. Adequate but not comprehensive.

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%, and the description restates the key parameters (combustible, anioMatriculacion). It adds no new semantics beyond the schema, so baseline 3 is appropriate.

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 the verb 'Calcula' and the resource 'etiqueta medioambiental DGT', enumerates possible labels. Also mentions additional ZBE access info and chainability with recomendar_vehiculo, distinguishing it from siblings like calcular_combustible.

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?

Usage context is implied (for environmental label), but there is no explicit when-to-use vs alternatives or exclusions. The chainability hint provides some guidance, but not enough for a higher score.

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