Skip to main content
Glama

Better Llama — Chile data

Chilexpress: coberturas, regiones, oficinas, cotizar y seguir envíos

chilexpress_shipping
Read-onlyIdempotent

Usa las APIs oficiales de Chilexpress: coberturas y códigos de comuna, regiones (sin clave), oficinas y puntos Pick Up, cotización de envíos entre comunas y seguimiento de órdenes de transporte. Cotizar y seguir requieren tus propias claves gratuitas de developers.wschilexpress.com (argumentos cotizadorKey/enviosKey/coberturasKey o encabezados X-Chilexpress-*-Key). No afiliado a Chilexpress. / Chilexpress coverage, offices, quotes and tracking.

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

Input Schema

NameRequiredDescriptionDefault
originNoOrigen / Origin — Comuna o código de cobertura (p. ej. «Santiago» o «STGO»).
comunasNoComunas / Communes — Filtra por comuna (sin tildes ni mayúsculas).
regionsNoRegiones / Regions — coberturas/oficinas: RM, R5…, número INE o nombre. Vacío = todo Chile.
widthCmNoAncho (cm) — Por defecto 10.
heightCmNoAlto (cm) — Por defecto 10.
lengthCmNoLargo (cm) — Por defecto 10.
maxItemsNoMáximo de resultados a devolver (1-200). Por defecto 20.
weightKgNoPeso (kg) — Por defecto 1.
enviosKeyNoClave «Envíos» — Tu clave personal y gratuita del proveedor (https://developers.wschilexpress.com). También puedes enviarla en un encabezado HTTP (ver la ficha de la herramienta). Se usa solo en esa solicitud; nunca se guarda ni se registra.
operationNoOperación / Operation — regiones y coberturas: sin clave. oficinas: clave «Coberturas» recomendada. cotizar: clave «Cotizador». seguimiento: clave «Envíos».coberturas
referenceNoReferencia (opcional) — Referencia del cliente asociada a la OT.
companyRutNoRUT de la empresa emisora — RUT de la empresa que generó las OT (con o sin dígito verificador). La API de Envíos solo permite seguir OT de tu propia empresa.
officeTypeNoTipo de oficina — Solo operation=oficinas.todas
showEventsNoIncluir todos los eventos — Si no, solo el estado actual.
environmentNoAmbiente / Environment — Las claves de prueba solo funcionan en «pruebas».produccion
productTypeNoProducto — Tipo de envío.encomienda
cotizadorKeyNoClave «Cotizador» — Tu clave personal y gratuita del proveedor (https://developers.wschilexpress.com). También puedes enviarla en un encabezado HTTP (ver la ficha de la herramienta). Se usa solo en esa solicitud; nunca se guarda ni se registra.
coverageTypeNoTipo de cobertura — comunas = una fila por comuna; sectores = localidades dentro de comunas; todas = ambas.comunas
deliveryTimeNoServicios — Qué servicios cotizar.todos
destinationsNoDestinos / Destinations — Una o más comunas o códigos (máx. 50).
coberturasKeyNoClave «Coberturas» — Tu clave personal y gratuita del proveedor (https://developers.wschilexpress.com). También puedes enviarla en un encabezado HTTP (ver la ficha de la herramienta). Se usa solo en esa solicitud; nunca se guarda ni se registra.
declaredValueNoValor declarado (CLP) — Por defecto 10000.
trackingNumbersNoNúmeros de OT / Tracking numbers — Órdenes de transporte a seguir (máx. 200).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world behavior, so the bar is lower, yet the description still adds real context: keys are supplied per request, never stored or logged, and are obtainable free from developers.wschilexpress.com. It does not describe response shape or rate limits, which keeps it below a 5.

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 scope is front-loaded before prerequisites and the disclaimer, and every sentence carries weight. The trailing English gloss 'Chilexpress coverage, offices, quotes and tracking' is largely redundant with the opening sentence.

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?

For a 23-parameter, five-mode tool with no output schema, the description covers authentication and operation selection well but says nothing about what each operation returns (coverage rows, office lists, quote fields, tracking events). An agent knows how to call it but not what to expect back.

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 every one of the 23 parameters is already documented, including the header alternative for keys. The description repeats the three key parameter names without adding format or interaction details beyond what the schema provides, matching the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names concrete verbs and resources — coberturas y códigos de comuna, regiones, oficinas y puntos Pick Up, cotización entre comunas, seguimiento de OT — so an agent immediately knows the five capabilities. It also states the provider (official Chilexpress APIs) and disclaims affiliation, leaving no ambiguity about the domain versus unrelated Chile-data siblings.

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 per-operation prerequisites (regiones/coberturas sin clave, oficinas recomienda clave «Coberturas», cotizar requiere «Cotizador», seguimiento requiere «Envíos») and tells the agent where to obtain keys. The environment note implicitly warns that test keys only work in «pruebas», but there is no explicit 'when not to use this tool' guidance.

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