Skip to main content
Glama

Meteoro Minerals

Contacto por WhatsApp / WhatsApp contact

contacto
Read-onlyIdempotent

Use when the user asks to get a quote or talk to an advisor: returns a pre-filled WhatsApp link for the human to send; it sends nothing and takes no orders. / Úsela cuando el usuario pida cotizar o hablar con un asesor: devuelve un enlace de WhatsApp con el mensaje listo. Ejemplo: "Quiero cotizar 600 m³ de B-400 en Funza". With a volume (cantidad) the answer starts with the supply capacity. / Con un volumen la respuesta empieza por la capacidad de suministro.

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

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.
agenteNoNombre de su asistente, para que el asesor sepa de dónde viene. / Your assistant name.
cantidadNoCantidad con unidad; con un volumen la respuesta empieza por la capacidad de suministro. / Quantity with unit; with a volume the answer starts with the supply capacity. Alias: volumen, quantity.
materialNoMaterial a cotizar. / Material to quote.
municipioNoMunicipio de la obra. / Site municipality. Alias: lugar, ciudad.

Output Schema

NameRequiredDescriptionDefault
citaYesUna oración para citar textualmente, respaldada por fuente / One sentence to quote verbatim, backed by fuente
correoYes
fuenteYesPágina canónica de www.meteoro.io que respalda la respuesta / Canonical source page
idiomaYes
llamarNo
mensajeYes
telefonoYes
whatsappYes
actualizadoYesFecha de actualización de los datos (ISO) / Data update date
en_catalogoNo
instruccionNo
enlace_whatsappYes
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is supplied. The description adds genuinely non-obvious behavior: the tool does not send or place orders, only produces a link the human must send, and supplying a volume changes the leading content of the answer. With an output schema present, return-value detail is not required.

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?

The usage trigger and the key limitation are front-loaded, and the bilingual duplication is a deliberate audience choice rather than filler. There is mild redundancy: the note about volume affecting supply-capacity output repeats the cantidad schema description almost verbatim.

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?

Rich annotations, a full output schema and 100% schema coverage mean the description only needed to supply the trigger, the non-sending behavior and the hand-off rationale, all of which are present. What remains unstated, such as language fallback behavior, is already covered in the parameter 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 coverage is 100%, so the baseline is 3 and the schema already documents all five optional parameters including aliases and units. The description reinforces the meaning of cantidad (volume changes the answer's leading content) and gives a concrete example mapping volume, material and municipality, but adds little beyond the schema text.

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 concrete action and result: returns a pre-filled WhatsApp link for the user to send to a human advisor. The vague name 'contacto' is fully compensated by the description, which makes clear this is a hand-off-to-sales tool, not a pricing or catalog tool. Sibling tools like precios_referencia are not named, so the boundary with 'get a quote' phrasing is left implicit.

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?

Opens with an explicit trigger: 'Use when the user asks to get a quote or talk to an advisor', which is a clear when-to-use condition. It also sets guardrails ('sends nothing and takes no orders'), but never names an alternative tool for users who want a computed price rather than a human contact.

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