Skip to main content
Glama

Better Llama — Chile data

Buscar herramientas de Better Llama

search_tools
Read-only

Busca entre las herramientas de datos de Latinoamérica de Better Llama por tarea o tema (p. ej. "precio bencina Ñuñoa", "licitaciones", "valor UF", "sismos"). Devuelve nombre, categoría, tipo de acceso y argumentos de ejemplo. Hoy cubre Chile; México, Perú, Colombia y Argentina están en el roadmap. / Find Better Llama tools by task.

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_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoQué necesitas hacer, en español o inglés. Vacío = todas.
categoryNoOpcional: filtra por categoría.

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?

The readOnlyHint and openWorldHint annotations already establish safety and scope, and the description adds useful behavior: it returns tool name, category, access type, and example arguments, and currently covers Chile only. It does not describe result limits or ranking, but the key behavioral context is present.

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 description is front-loaded with the main action and examples, and the coverage note is useful. The final English sentence partly duplicates the Spanish opening, but the overall structure remains efficient.

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 a read-only discovery tool with no output schema, the description explains what is returned and what geography is currently covered. It is nearly complete, though it could optionally clarify result ordering or whether all matches are returned.

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 the query and category parameters are already well documented in the input schema. The description adds concrete example queries and notes the geographic scope, but does not add syntax or filtering semantics beyond what the schema provides.

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 states a specific verb and resource: it searches Better Llama's Latin American data tools by task or topic. It also clarifies the return shape (name, category, access type, sample arguments), so an agent can tell this is a discovery tool rather than a data-fetching sibling.

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 description gives clear usage context through examples such as fuel prices, tenders, UF value, and earthquakes, and states current geographic coverage. It does not explicitly say when not to use this tool or name specific sibling alternatives, so it falls short of full routing 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