Skip to main content
Glama

Meteoro Minerals

Verificar cobertura / Check coverage

verificar_cobertura
Read-onlyIdempotent

Use when the user asks whether Meteoro Minerals delivers to a Colombian municipality or department: returns the coverage answer with the coverage page section as source. / Úsela cuando el usuario pregunte si Meteoro Minerals entrega en un municipio o departamento. Ejemplo: "¿Entregan en Funza?".

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": {
      "lugar": "<lugar>"
    },
    "name": "verificar_cobertura"
  }
}

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.
lugarYesMunicipio, ciudad o departamento de la obra. / Site municipality, city or department. Alias: municipio, ciudad.
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.
departamentoNoDepartamento de la obra, si lo conoce. / Department, if known.

Output Schema

NameRequiredDescriptionDefault
citaYesUna oración para citar textualmente, respaldada por fuente / One sentence to quote verbatim, backed by fuente
notaYes
zonaNo
lugarYes
zonasYes
fuenteYesPágina canónica de www.meteoro.io que respalda la respuesta / Canonical source page
idiomaYes
cubiertoYes
whatsappYes
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
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that by disclosing the answer's provenance ('the coverage page section as source'), which tells the agent the response is grounded in a fixed coverage page rather than a live 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?

Two compact sentences, one per language, with the trigger front-loaded ahead of the example. There is no filler; the bilingual duplication is justified by the tool's es/en audience rather than being redundancy.

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?

An output schema exists, so return values need no explanation, and the four parameters are fully documented in the schema. The description supplies the trigger and the answer's source, which is sufficient for a simple single-lookup tool. It would be stronger with a note on partial matches or uncovered locations, but nothing critical is missing.

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% and all four parameters carry bilingual descriptions and alias lists, so the description need not restate them. It adds no semantics of its own (e.g. how 'lugar' interacts with 'departamento', or what happens when the location is not covered), leaving it at the baseline.

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?

The description states a specific resource and outcome: it answers whether Meteoro Minerals delivers to a given Colombian municipality or department and returns the coverage result with its page section as source. That is unambiguous. It does not explicitly position itself against siblings such as contacto or preguntas_frecuentes, so it stops short of a 5.

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 trigger is explicit and concrete: 'Use when the user asks whether Meteoro Minerals delivers to a Colombian municipality or department', reinforced by a worked example ('¿Entregan en Funza?'). It gives no when-not conditions and names no alternative tool for related questions such as pricing or product availability, which keeps it below 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