Skip to main content
Glama

Better Llama — Chile data

Diario Oficial de Chile: normas, avisos y sociedades

search_chile_official_gazette
Read-onlyIdempotent

Busca publicaciones del Diario Oficial de Chile por fecha o rango (máx. 31 días): normas generales y particulares, avisos destacados y empresas y cooperativas (constituciones, modificaciones, disoluciones de sociedades), con filtros por tipo de sociedad y palabras clave. Cada resultado trae CVE, enlace al PDF oficial y atribución. Excluye publicaciones judiciales y marcas por privacidad. / Search Chile Official Gazette publications.

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

Input Schema

NameRequiredDescriptionDefault
toDateNoHasta (AAAA-MM-DD) — Vacío = hoy (hora de Chile).
fromDateNoDesde (AAAA-MM-DD) — Vacío = misma fecha que 'Hasta'. Máximo 31 días por llamada.
keywordsNoPalabras clave — Filtra por título, institución o categoría (sin tildes ni mayúsculas). Coincide si aparece cualquiera.
maxItemsNoMáximo de resultados a devolver (1-200). Por defecto 30.
sectionsNoSecciones — Vacío = todas.
empresaActsNoActos societarios (Empresas) — Filtra la sección Empresas y Cooperativas. Vacío = todos.
companyTypesNoTipo de sociedad contiene — Texto, p. ej. 'Acciones' (SpA), 'Anónimas', 'Responsabilidad Limitada', 'Individuales', 'Cooperativas'.
includeExtraordinaryNoIncluir ediciones extraordinarias — Ediciones con sufijo -B, -C, etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the bar is lower; the description still adds real context beyond them — the 31-day call cap, the coverage exclusions, and the fact that each result carries CVE, the official PDF link and attribution. It does not discuss rate limits or what happens with empty result sets, which is the only notable omission.

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 opening sentence front-loads the verb, resource and date constraint before enumerating content types and filters in a single dense but readable clause. The trailing English sentence is a lightweight bilingual anchor rather than padding, though the whole entry is longer than strictly necessary.

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?

For an 8-parameter, zero-required filtering tool with no output schema, the description supplies the return shape (CVE, PDF link, attribution), the date-window limit and the excluded material, which is what an agent needs to call it correctly. It could still note default page sizing behavior, but nothing essential is missing.

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 parameter (dates, keywords, maxItems, sections, empresaActs, companyTypes, includeExtraordinary) is already documented with defaults and limits. The description only restates that filtering exists by company type and keywords, adding no syntax or interaction rules beyond the schema, so baseline 3 applies.

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?

Specific verb plus resource ("Busca publicaciones del Diario Oficial de Chile") immediately followed by the scope: date or range, and the four content classes (normas generales/particulares, avisos, empresas y cooperativas) with their filters. No sibling does gazette search, so the tool's identity is unambiguous from the first clause.

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 states the operating constraint ("por fecha o rango (máx. 31 días)") and explicit scope exclusions ("Excluye publicaciones judiciales y marcas por privacidad"), which tells the agent when results will be missing. What it lacks is any explicit routing statement such as when to prefer a narrower or different tool, so it stops short of a full when/when-not guide.

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