Skip to main content
Glama

Meteoro Minerals

Preguntas frecuentes del sitio / Site Q&A

preguntas_frecuentes
Read-onlyIdempotent

Use when the user asks a buying question in their own words and no other tool fits exactly (where to buy, documents to ask a supplier for, IDU, RCD rules in Bogotá, quantities per truck, what Meteoro Minerals is): searches every question answered on www.meteoro.io and returns question, answer and the page#anchor to cite. / Úsela cuando el usuario haga una pregunta de compra con sus palabras y ninguna otra herramienta encaje: busca en las preguntas respondidas del sitio y devuelve pregunta, respuesta y fuente.

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": "preguntas_frecuentes"
  }
}

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.
limiteNoNúmero máximo de respuestas (1 a 10, por defecto 3). / Maximum answers (1 to 10, default 3). Alias: limit, max.
consultaYesPregunta o palabras clave, como las escribiría el comprador. / Question or keywords, as the buyer would type them. Alias: pregunta, question.

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
consultaYes
whatsappYes
resultadosYes
actualizadoYesFecha de actualización de los datos (ISO) / Data update date
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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds only the answer shape and its citation anchor, which is largely redundant with the declared output schema, and says nothing about ranking, empty-result behavior, or result breadth beyond 'searches every question'.

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-loaded with the usage condition and scoped in one sentence per language, with no filler. The cost is bilingual duplication, which roughly doubles length without adding new information for a reader who parses both halves.

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 and full parameter documentation, the description only needs to justify selection and scope, which it does. What remains thin is behavioral detail on result relevance and citation fidelity — helpful but not essential for correct invocation.

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% with per-parameter descriptions and aliases, so the schema carries the load. The description adds a light hint that queries should be phrased in the buyer's own words and that this is a buying-question corpus, but no syntax, keyword, or limit guidance 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?

States a specific verb and resource — it searches every question answered on www.meteoro.io — and explicitly names the retrieval output (question, answer, page#anchor). The 'no other tool fits exactly' framing positions it distinctly against the catalogue/technical-sheet siblings.

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 a clear trigger condition ('user asks a buying question in their own words') plus a fallback rule when no sibling matches, and enumerates the topic territory (where to buy, documents, IDU, RCD rules, quantities, what Meteoro Minerals is). It stops short of naming which specific sibling to prefer when one does fit, leaving that inference to the agent.

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