Skip to main content
Glama

Meteoro Minerals

Precios de referencia / Reference prices

precios_referencia
Read-onlyIdempotent

Use when the user asks how much a material costs: returns only the published reference prices, at origin and before VAT, with their month; never totals. / Úsela cuando el usuario pregunte cuánto cuesta un material: solo precios de referencia publicados, en origen y antes de IVA. Ejemplo: "¿Cuánto vale el recebo?".

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

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.
familiaNoLínea de producto a consultar; si se omite, todas. / Product line; all when omitted.

Output Schema

NameRequiredDescriptionDefault
citaYesUna oración para citar textualmente, respaldada por fuente / One sentence to quote verbatim, backed by fuente
reglaNo
fuenteYesPágina canónica de www.meteoro.io que respalda la respuesta / Canonical source page
idiomaYes
monedaYes
preciosYes
whatsappYes
condicionNo
actualizadoYesFecha de actualización de los datos (ISO) / Data update date
precio_realYes
iva_incluidoYes
vigente_hastaYes
iva_porcentajeNo
mes_referenciaYes
otros_materialesNo
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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add data semantics — and it does: prices are published, at origin, pre-VAT, month-tagged, and never aggregate totals. That prevents an agent from presenting them as final invoiced costs. It does not mention currency units or per-unit basis, which are relevant for this tool.

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 trigger condition is front-loaded and the second sentence delivers the return semantics economically. The bilingual duplication roughly doubles length, but that is justified for a tool explicitly serving Spanish and English queries.

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 zero required parameters, full schema coverage, an output schema for the return shape, and annotations covering safety, the description supplies what structured fields cannot: the trigger condition and the pre-VAT/origin/no-totals caveat. Only the unit basis and currency are left implicit.

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 both optional parameters (lang, familia) are fully documented with enums, examples, and aliases in the schema itself. The description adds no further meaning about these parameters, which is the baseline-3 case when the schema carries the load.

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 verb and resource: it returns published reference prices, at origin and before VAT, each with its month, and explicitly never totals. That scoping tells an agent this is a price-lookup, not a catalog search. It does not name any sibling tool to contrast with, so it falls short of full 5-level differentiation.

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?

It gives an explicit trigger condition — 'Use when the user asks how much a material costs' — and reinforces it with a concrete example query ('¿Cuánto vale el recebo?'). There are no when-not conditions or named alternatives, but the positive routing guidance is unambiguous.

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