Skip to main content
Glama

Meteoro Minerals

Consultar norma / Look up a standard

consultar_norma
Read-onlyIdempotent

Use when the user asks which standard (IDU, INVIAS, EAAB) applies to a material or pavement layer, the INVIAS requirements or gradations of granular base or subbase (CBR, plasticity index, SBG-50, SBG-38, BG-40, BG-38, BG-27, BG-25), or the difference between B-200, B-400 and B-600 or base and subbase: returns the catalog material that covers it, the side-by-side table from the data sheets and, for base or subbase, the INVIAS 2013 tables (320-2, 320-3, 330-3) with their citation and the guide page#anchor as fuente. / Úsela cuando el usuario pregunte qué norma aplica a un material o capa, o la diferencia entre B-200, B-400 y B-600 o entre base y subbase. Ejemplo: "¿Qué base uso en una vía INVIAS?".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "consultar_norma"
  }
}

Input Schema

NameRequiredDescriptionDefault
usoNoUso o capa: subbase, base, relleno, afirmado, zanjas de redes. / Use or layer.
langNoIdioma de la respuesta; si se omite, se usa el idioma de la consulta. / Answer language; defaults to the language of the query. Alias: idioma, language, locale.
normaNoEntidad cuya norma rige la obra. / Body whose standard governs the project.
materialNoMaterial del pliego o de la consulta. / Material from the bid or question. Alias: producto, product.

Output Schema

NameRequiredDescriptionDefault
citaYesUna oración para citar textualmente, respaldada por fuente / One sentence to quote verbatim, backed by fuente
notaYes
avisoNo
fuenteYesPágina canónica de www.meteoro.io que respalda la respuesta / Canonical source page
idiomaYes
whatsappYes
actualizadoYesFecha de actualización de los datos (ISO) / Data update date
norma_inviasNoINVIAS 2013 tables for granular base or subbase, with citation, edition note and compliance notice / INVIAS 2013 tables with citation
recomendadosYes
mapa_verificadoYes
ignored_argumentsNoArgumentos recibidos que no se usaron (desconocidos o reemplazados por el nombre canónico) / Received arguments that were not used
materiales_con_normaNo
especificacion_catalogoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is fully covered by structured data. The description adds what the response is composed of (catalog material, side-by-side table from data sheets, INVIAS 2013 tables 320-2/320-3/330-3 with citation and page#anchor as fuente), which is genuine behavioral context, but since an output schema exists this is partly restating return content rather than disclosing non-obvious traits like fallback behavior when no standard matches.

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

Conciseness3/5

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

Front-loaded with the trigger and organized as when-to-use clause plus a return-content clause, which is good structure. However, the entire content is duplicated in Spanish, roughly doubling length, and the long parenthesised enumeration of codes (SBG-50, BG-40, 320-2, 330-3) makes the single sentence dense and harder to parse.

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?

For a domain-lookup tool with an output schema, full annotation coverage and 100% schema descriptions, the definition supplies enough: trigger conditions, the scope of standards covered, and the shape of the answer. Missing only fallback/no-match behavior and explicit sibling disambiguation.

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%: uso, norma and material all carry bilingual descriptions and examples, and norma/lang have enums. The description adds no parameter-level meaning beyond naming the same material/layer concepts, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('consultar norma / look up a standard') and enumerates the exact question classes it answers (which standard applies, INVIAS gradations, B-200 vs B-400 vs B-600, base vs subbase). It is highly concrete, but it never names a sibling tool, so the agent must infer the boundary with buscar_catalogo or ficha_tecnica on its own.

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 opening 'Use when the user asks...' clause plus a concrete example question ('¿Qué base uso en una vía INVIAS?') gives an unambiguous trigger. There is no when-not guidance and no mention of which sibling handles adjacent lookups, so routing away from near-neighbours is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources