Skip to main content
Glama

Meteoro Minerals

Legalidad del proveedor / Supplier legality

legalidad
Read-onlyIdempotent

Use when the user asks whether Meteoro Minerals is a legal supplier, its RUCOM, its ISO certificates or how to verify them in the ANM public registry. / Úsela cuando el usuario pregunte si Meteoro Minerals es legal, por su RUCOM, sus certificaciones ISO o cómo verificarlas. Ejemplo: "¿Meteoro Minerals tiene RUCOM?".

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

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.

Output Schema

NameRequiredDescriptionDefault
isoYes
nitYes
citaYesUna oración para citar textualmente, respaldada por fuente / One sentence to quote verbatim, backed by fuente
rucomYes
fuenteYesPágina canónica de www.meteoro.io que respalda la respuesta / Canonical source page
idiomaYes
empresaYes
whatsappYes
actualizadoYesFecha de actualización de los datos (ISO) / Data update date
razon_socialYes
trazabilidadNo
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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful behavioral detail that the claims are verifiable against the ANM public registry, but says nothing about how current or cached the certificate/RUCOM data is, which matters for a compliance answer.

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 "Use when", then the Spanish mirror and a short example; nothing extraneous. The bilingual duplication is inherent to a bilingual tool rather than filler, though the sample question is close to redundant with the trigger sentence.

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 only one optional parameter needs covering. For a compliance-lookup tool the description is nearly complete; the only gap is that it never indicates whether the reported ISO/RUCOM status is authoritative or how stale it might be.

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?

With one optional parameter and 100% schema description coverage, the schema fully documents lang, its enum, its default-to-query-language behavior and its aliases. The description adds no parameter meaning beyond that, 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 names a concrete resource: Meteoro Minerals' legal status, RUCOM, ISO certificates, and ANM public-registry verification. It is framed as a trigger ("Use when the user asks whether...") rather than as an output statement, but an agent can still tell this is the supplier-legality lookup and distinguish it from siblings like ficha_tecnica or precios_referencia.

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?

Explicit when-to-use conditions are given, reinforced by a concrete sample question ("¿Meteoro Minerals tiene RUCOM?"). No when-not-to-use or named alternatives appear, so routing away from this tool is left to inference.

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