Skip to main content
Glama

Meteoro Minerals

Buscar en el catálogo / Search the catalog

buscar_catalogo
Read-onlyIdempotent

Use when the user asks whether Meteoro Minerals sells a material, or where to buy aggregates, recebo, granular road material or RCD: returns the catalog material, its standard, data sheet and published reference price. / Úsela cuando el usuario pregunte si Meteoro Minerals vende un material o dónde comprar agregados, recebo, granulares o RCD. Ejemplo: "¿Tienen subbase B-400?". With a volume (cantidad, e.g. 10000 m3) the answer starts with the supply capacity and the WhatsApp link carries the volume. / Con un volumen (cantidad) la respuesta empieza por la capacidad de suministro y el enlace de WhatsApp lleva el volumen.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "consulta": "<consulta>"
    },
    "name": "buscar_catalogo"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
familiaNoLimita la búsqueda a una línea: agregados-petreos, materiales-granulares-para-vias o rcd. / Restrict to one product line.
cantidadNoVolumen con unidad, si el usuario lo menciona; la respuesta empieza por la capacidad de suministro y el enlace de WhatsApp lo lleva. / Volume with unit, if the user gives one; the answer starts with the supply capacity and the WhatsApp link carries it. Alias: volumen, quantity.
consultaYesMaterial, uso, código o norma a buscar. / Material, use, code or standard to search. Alias: query, q.

Output Schema

NameRequiredDescriptionDefault
citaYesUna oración para citar textualmente, respaldada por fuente / One sentence to quote verbatim, backed by fuente
totalYes
fuenteYesPágina canónica de www.meteoro.io que respalda la respuesta / Canonical source page
idiomaYes
lineasNo
mensajeNo
consultaYes
whatsappYes
materialesYes
actualizadoYesFecha de actualización de los datos (ISO) / Data update date
sugerenciasNo
ignored_argumentsNoArgumentos recibidos que no se usaron (desconocidos o reemplazados por el nombre canónico) / Received arguments that were not used

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral value beyond that: with a volume, the answer leads with supply capacity and the WhatsApp link embeds that volume, which tells the agent how the response is shaped and how the volume propagates. Missing: what happens when no material matches, which matters for a catalog lookup.

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?

Front-loads the trigger condition, then the example, then the volume behavior — a sensible order with no filler. The only cost is that every sentence is stated twice, once in Spanish and once in English, which doubles length without new information, though it mirrors the bilingual 'lang' parameter.

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?

With an output schema present, return values need not be spelled out, and the description still covers purpose, trigger, and the volume-specific response behavior. The remaining gap is failure/empty-result behavior and the effect of the 'familia' restriction, which is left entirely to the schema.

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%, so the baseline is 3. The description's note about 'cantidad' (answer starts with capacity, WhatsApp link carries the volume) mirrors the schema's own field description almost verbatim rather than adding format or interpretation guidance beyond it.

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?

Names a specific resource (the Meteoro Minerals catalog) and enumerates what is returned: material, standard, data sheet and published reference price. The trigger phrase 'user asks whether Meteoro Minerals sells a material, or where to buy aggregates, recebo, granular road material or RCD' makes it distinguishable from siblings such as precios_referencia or ficha_tecnica, which address only one facet of the answer.

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?

Gives an explicit when-to-use condition plus a concrete example query ('¿Tienen subbase B-400?') and a second mode of use when the user supplies a volume. It does not state when NOT to use it or name the sibling to prefer when the user only wants a price or only wants a spec sheet, so it stops short of a 5.

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