Skip to main content
Glama
mcp-direcciones-ar

mcp-direcciones-ar

geocodificar_inverso

Converts latitude and longitude into the nearest Argentine street address; returns null if the point has no associated address.

Instructions

Devuelve la dirección argentina más cercana a un punto (latitud, longitud). Si el punto no tiene una dirección asociada, devuelve null.

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": {
      "latitud": "<latitud>",
      "longitud": "<longitud>"
    },
    "name": "geocodificar_inverso"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudYes
longitudYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 behavioral burden, and it does disclose the key edge case: returning null when the point has no associated address. It also frames the result as 'nearest', implying approximate rather than exact matching. It says nothing about accuracy radius, whether points outside Argentina return null, or authentication/rate-limit behavior.

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?

Two sentences with no filler, front-loading the main behavior and then the null fallback. It is efficient, though the second sentence could be folded into the first without any loss.

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 two-parameter read-only lookup with no output schema, the description covers what an agent most needs: what comes back (an Argentine address) and what comes back when nothing matches (null). With annotations absent, it could say more about permissions or accuracy guarantees, but for this tool's complexity it is largely sufficient.

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 0%, so the description must compensate, but it only restates the parameter names '(latitud, longitud)'. The schema itself supplies the numeric type and the -90/90 and -180/180 bounds, so the agent can infer degrees and valid ranges from structured data alone. No precision, format, or coordinate-order guidance is added beyond that.

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?

States a specific verb and resource: it returns the nearest Argentine address for a lat/long point, which is clearly reverse geocoding and clearly scoped to Argentina. It does not explicitly contrast itself with the sibling buscar_direccion, so the agent must infer that this is the coordinate-to-address direction rather than the address-to-coordinate direction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent must already know it has coordinates and wants an address to select this tool. There is no explicit when-to-use, no mention of buscar_direccion as the forward-geocoding alternative, and no stated prerequisites such as the point having to fall inside Argentina.

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