Direcciones AR

Buscar localidades argentinas

buscar_localidad

Busca localidades (ciudades, pueblos, barrios censales) por nombre aproximado y devuelve provincia, departamento/partido, municipio, categoría y coordenadas del centroide, con ids oficiales INDEC. Útil para desambiguar ('¿qué Rosario?'), completar formularios o resolver la ubicación de un cliente. Filtrá por provincia cuando la conozcas. Costo: 1 crédito(s).

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": {
      "nombre": "<nombre>"
    },
    "name": "buscar_localidad"
  }
}

Input Schema

Name	Required	Description
`max`	No
`nombre`	Yes	Nombre (tolera tildes y errores leves)
`provincia`	No	Nombre o id de provincia
`departamento`	No	Departamento o partido

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the load and does so reasonably: it states the cost (1 crédito), that matching is approximate, and what each result contains (official INDEC ids, centroid coordinates). It omits auth/permission requirements and failure or empty-result behavior, but for a read-only lookup that is a minor gap.

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?

Single front-loaded paragraph that opens with what is searched, then return fields, then use cases, then a filtering tip and cost. Every sentence contributes; only the parenthetical example is expendable.

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?

No output schema exists, so describing the returned fields (provincia, departamento/partido, municipio, categoría, centroid coordinates, INDEC ids) is necessary and present. Cost and the fuzzy-match tolerance are covered; only edge-case behavior is 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 coverage is 75%, so nombre, provincia and departamento are already documented. The description reinforces the fuzzy name matching and advises using the province filter, but says nothing about the max parameter or the id-vs-name acceptance for provincia, so it adds only marginal meaning beyond the schema.

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 gives a specific verb and resource ('Busca localidades') and delimits what counts as a locality (ciudades, pueblos, barrios censales), plus the approximate-name matching mode. It does not explicitly contrast itself with siblings like buscar_division or ubicacion, so an agent must infer that this is the gazetteer lookup rather than a street or address lookup.

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 names concrete use cases (disambiguating '¿qué Rosario?', filling forms, resolving a client's location) and adds a conditional recommendation ('Filtrá por provincia cuando la conozcas'). There are no explicit exclusions or named alternatives, which keeps it short of a 5.

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

All Direcciones AR tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?