Skip to main content
Glama
mcp-direcciones-ar

mcp-direcciones-ar

buscar_direccion

Search Argentine street addresses from free text to autocomplete address fields, returning street, number, neighborhood, locality, and coordinates; an empty list means no matches.

Instructions

Busca direcciones argentinas por texto libre y devuelve calle, altura, barrio, localidad y coordenadas. Sirve para autocompletar un campo de dirección. Una lista vacía significa que no hay coincidencias.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "consulta": "<consulta>"
    },
    "name": "buscar_direccion"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNoCuántos resultados devolver (1 a 10, por defecto 5).
consultaYesTexto a buscar, por ejemplo "rivadavia 5000 caballito".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses the return fields and that an empty list means no matches. It says nothing about ordering, partial-match behavior, rate limits, or authentication, leaving meaningful behavioral gaps for a search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose and return fields, then the use case, then the empty-result semantics. No wasted wording.

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 simple two-parameter read tool with no output schema, the description compensates by listing the returned fields and explaining the empty-list case. Only minor behavioral details (ordering, match quality) are absent.

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 parameters (consulta, limite) are already documented in the schema. The description adds no syntax or format detail beyond what the schema provides, so the 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?

States a specific verb and resource ("Busca direcciones argentinas por texto libre") and enumerates the returned fields (calle, altura, barrio, localidad, coordenadas). The "texto libre" framing implicitly separates it from the reverse-geocoding sibling geocodificar_inverso.

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?

Gives a clear use case ("Sirve para autocompletar un campo de dirección"), which tells the agent when this tool fits. It stops short of naming the alternative or stating when not to use it, so it is clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools