Skip to main content
Glama

Ground a location

ground_location
Read-onlyIdempotent

Get location grounding in one call: reverse-geocoded address, surrounding categories, reachable-area stats, and nearby notable places from lat/lon or a place name.

Instructions

One-hop location grounding: where, surroundings, reach, notable.

Answers "orient me at this point" in a single call instead of chaining
a reverse lookup, an area summary, a reachable-area scan, and a
nearby-places search. Give the point as lat/lon, or as `where` — a
{"lat", "lon"} dict, a GERS id, or a free-text place name — but not
both (and not neither); either way returns {"error": "bad_request"}
naming the choice. A `where` given as an id/name adds a compact
"resolved": {"name", "id", "lat", "lon", "matched_by"} to the answer
(a separate key from the answer's own "where" section below); absent
for lat/lon or a {lat,lon} where. Returns:
- where: reverse_geocode's answer for the point (address/divisions
  chain, or a "divisions_only" degrade).
- surroundings: total places and the top few categories within a fixed
  500m radius, plus density_per_km2.
- reach: reachable-area stats only for (minutes, mode) —
  {reachable_nodes, max_radius_m, area_km2}. Never includes the
  reachable-area polygon; this tool returns no geometry, ever.
- notable: the nearest 2-3 named places, no category filter.

Each section is independent: if its underlying call fails or comes
back empty, that section is dropped and a short line explaining why is
added to "notes" instead — the call only fails outright if every
section failed, returning a structured {"error":
"upstream_unavailable", ...}.

minutes must be > 0 and <= 60; omit mode to use the stored
preferences mode, else walk.
Both, plus out-of-range coordinates, return {"error": "bad_request"}.
No confirm gate: the reach scan runs with the requested minutes/mode
as-is (it self-caps its graph extraction radius; no nearby street
graph just degrades the reach section to a note).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNo
lonNo
modeNoTravel mode. Default: stored preference, else walk.
whereNo
minutesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark the tool as readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond that: per-section independent failure with notes, structured bad_request vs upstream_unavailable errors, no geometry ever returned, no confirm gate, self-capping of the graph extraction radius, and degradation of the reach section to a note. This far exceeds the baseline.

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 long but well-organized with a one-line summary, clear return-section bullets, and a short list of edge cases. It front-loads the core purpose and keeps related facts grouped. It loses one point because a few details are slightly redundant, such as repeating the mode default that already appears in the schema and restating bad_request behavior in two places.

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?

Given the tool's complexity, the description is remarkably complete: it covers input cardinality, accepted formats, bounds, error modes, per-section degradation, and even the deliberate absence of geometry. An agent has everything needed to invoke this tool correctly and to interpret unexpected per-section outcomes, especially with an output schema also present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%, but the description compensates thoroughly. It explains the mutually exclusive lat/lon vs where inputs and the bad_request result when both or neither are supplied, enumerates valid where forms (dict, GERS id, free-text name), explains the resolved key, constrains minutes to (0, 60], and clarifies mode default behavior. This is exactly the semantic guidance the sparse schema lacks.

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-plus-resource: 'Ground a location' with 'One-hop location grounding: where, surroundings, reach, notable.' It clearly distinguishes itself from sibling chainable tools by promising a single call that replaces a reverse lookup, area summary, reachable-area scan, and nearby-places search. The purpose is unmistakable.

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 explicitly identifies when to use the tool: 'Answers "orient me at this point" in a single call instead of chaining' the four underlying operations. This gives an agent a concrete decision rule and names the alternatives it replaces, without requiring it to infer from sibling names alone.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chuofringer/placeroot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server