Skip to main content
Glama

Meteoro Minerals

Ficha técnica / Data sheet

ficha_tecnica
Read-onlyIdempotent

Use when the user asks for the data sheet of a material: code, standard, uses, unit, published reference price and test values only where published. / Úsela cuando el usuario pida la ficha técnica de un material. Ejemplo: "Ficha técnica de B-400 IDU".

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": {
      "material": "<material>"
    },
    "name": "ficha_tecnica"
  }
}

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.
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.
materialYesNombre, código (MM-...) o slug de la ficha. / Name, code or slug of the data sheet. Alias: producto, product.

Output Schema

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile needs no restating. The description does add one genuinely useful behavioral nuance – that reference price and test values are returned 'only where published' – but it says nothing about what happens when no sheet matches a material or how large the result is.

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 sentences, front-loaded with the trigger condition and followed by a concrete example; nothing is wasted. The bilingual duplication is justified for a Spanish/English tool but does double the length without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 cover selection and edge cases. It covers selection adequately but omits what to do on a miss (no matching sheet, ambiguous material name) and leaves the overlap with precios_referencia and buscar_catalogo unresolved.

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 each parameter (material, lang, cantidad) already carries its own description, aliases and examples. The description adds no parameter-level meaning of its own beyond the output field list, so the 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?

The description states a specific resource and enumerates the fields returned (code, standard, uses, unit, published reference price, test values), which makes the tool's scope concrete. It does not, however, contrast itself with plausible siblings such as buscar_catalogo or precios_referencia, so the agent must infer the boundary.

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 for the data sheet of a material' plus a worked example ("Ficha técnica de B-400 IDU") gives a clear triggering condition. It stops short of exclusions or alternatives – it never says to use precios_referencia when only a price is wanted or buscar_catalogo when the material name is unknown.

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