Skip to main content
Glama

Address of a point

bl_reverse_geocode
Read-onlyIdempotent

Convert latitude and longitude coordinates into a Persian street address with city, county, and neighbourhood for locations in Iran.

Instructions

Turn coordinates into a Persian street address with city, county and neighbourhood (reverse geocoding).

For the opposite (name -> coordinates) use bl_search. Iran only; elsewhere it errors.

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": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "bl_reverse_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude, e.g. 35.7448.
lngYesLongitude, e.g. 51.3753.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude in degrees, e.g. 35.7448."New value: +"Latitude, e.g. 35.7448."
    • changedInput schema / properties / lng / description
      Previous value: -"Longitude in degrees, e.g. 51.3753."New value: +"Longitude, e.g. 51.3753."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and idempotency are covered. The description still adds value beyond them: the Iran-only geographic constraint and the fact that out-of-scope input produces an error rather than empty results, plus the shape of the returned address. It stops short of mentioning rate limits or what an unmatched coordinate returns, so it is not fully exhaustive.

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?

Two sentences, zero filler. The core operation and its return fields come first, followed by the disambiguation and the coverage constraint, which is the right front-loading for an agent skimming tool lists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, fully-required, no-output-schema read tool, the description supplies everything needed: the transformation, the return components, the inverse tool, and the geographic failure mode. Annotations carry the safety profile, so nothing material 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% and both lat/lng carry example values and min/max bounds, so the schema does the parameter work. The description adds no syntax or format detail for the coordinates beyond implying they are a point pair. Baseline 3 applies when the schema already documents everything.

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 names a specific verb and transformation ("Turn coordinates into a Persian street address") and enumerates the returned components (city, county, neighbourhood), plus labels it as reverse geocoding. It also names the sibling it is not (bl_search), so the agent can separate it from the other lookup tool without opening a schema.

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

Usage Guidelines5/5

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

It gives an explicit alternative for the inverse operation ("For the opposite (name -> coordinates) use bl_search") and states a hard applicability boundary ("Iran only; elsewhere it errors"). Both the when-to-use and when-not-to-use cases are covered in two short clauses.

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