Integrates with Hermes Agent to deliver real-time location labeling, including place names, categories, and opening hours via the GeoLabel API.
Turn GPS coordinates into AI-ready location context — for Claude Desktop, Claude Code, and any MCP-compatible assistant.
Send coordinates. Get back a place name, category, and real-time opening hours:
{
"label": "Walmart",
"category": "supermarket",
"is_open": true,
"closes_at": "23:00",
"opening_hours": "Mo-Su 06:00-23:00"
}Claude can then answer: "You're at Walmart, which closes in 47 minutes."
Related MCP server: Geo MCP Worker
Free at geolabel.dev — 100 requests/day, no credit card required.
Pick your client below.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"geolabel": {
"command": "uvx",
"args": ["geolabel-mcp"],
"env": {
"GEOLABEL_API_KEY": "glk_your_key_here"
}
}
}
}Restart Claude Desktop. The GeoLabel tool will appear in the tools list.
claude mcp add geolabel -- uvx geolabel-mcp
export GEOLABEL_API_KEY=glk_your_key_hereEdit ~/.hermes/config.json:
{
"mcpServers": {
"geolabel": {
"command": "uvx",
"args": ["geolabel-mcp"],
"env": {
"GEOLABEL_API_KEY": "glk_your_key_here"
}
}
}
}See Hermes Agent MCP docs for more.
# Register the server
openclaw mcp set geolabel \
--command uvx \
--args geolabel-mcp \
--env GEOLABEL_API_KEY=glk_your_key_here
# Verify it's registered
openclaw mcp listSee OpenClaw MCP docs for more.
You: I'm at 41.8827, -87.6233 — what's here and is it open?
Agent: You're at Planet Fitness (a gym). It's currently open and closes
at 11:00 PM tonight — you have about 3 hours left.get_location_labelIdentifies the nearest named place within radius metres of the given coordinates.
Parameter | Type | Default | Description |
| float | required | Latitude (-90 to 90) |
| float | required | Longitude (-180 to 180) |
| int | 100 | Search radius in metres (max 500) |
Response fields:
Field | Type | Description |
| string | null | Raw venue name from OpenStreetMap |
| string | Clean, display-ready name |
| string | null | Stable type: |
| float | null | Distance from your coordinates to the place |
| bool | null |
|
| string | null | Next opening time |
| string | null | Today's closing time |
| string | null | Raw OSM |
| bool | Served from 10-min cache; hours always recalculated live |
# pip
pip install geolabel-mcp
# run directly
GEOLABEL_API_KEY=glk_xxx geolabel-mcpclaude mcp add geolabel -- uvx geolabel-mcpThen set your key:
# add to your shell profile or .env
export GEOLABEL_API_KEY=glk_your_key_hereVariable | Required | Description |
| Yes | Your GeoLabel API key |
| No | Override API base URL (default: |
GeoLabel strips coordinates from all server logs before they touch disk. No movement history is stored. Data is processed in real-time and immediately discarded. Full privacy policy →
MIT
Identify a place from GPS coordinates and return its label, category, and live opening-hours status.
Use this whenever the user provides coordinates or asks what is at a location. The response gives Claude everything needed to answer location-aware questions — place name, type, whether it is open right now, and when it closes or next opens.
Args: lat: Latitude in decimal degrees (-90 to 90). lng: Longitude in decimal degrees (-180 to 180). radius: Search radius in metres. Smaller values pin to the nearest place precisely; larger values cast a wider net. Default 100 m, maximum 500 m.
Returns a dict with: place Raw venue name from OpenStreetMap (may include branch numbers or location suffixes). Prefer 'label' for display. label Clean, user-friendly name — e.g. "Walmart", "Planet Fitness", "Starbucks". Use this for display and speech. category Stable place type for logic: "gym", "supermarket", "restaurant", "fast_food", "gas_station", "pharmacy", "hospital", "cafe", "retail", etc. distance_meters Distance in metres from the supplied coordinates to the matched place centroid. is_open true → currently open. false → currently closed. null → OpenStreetMap has no hours data for this place. opens_at Next opening time as "HH:MM" (24-hour). Populated when is_open is false so you know when it reopens. null when open, or when hours are unknown. closes_at Today's closing time as "HH:MM" (24-hour). Populated when is_open is true — subtract current time to get minutes remaining. null when closed or hours unknown. opening_hours Raw OpenStreetMap opening_hours string, e.g. "Mo-Fr 09:00-18:00; Sa 10:00-17:00". null if not set in OSM. cached true if place data was served from the 10-minute in-memory cache. Hours fields are always recalculated live against the current time, even on cache hits.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | Yes | ||
| lng | Yes | ||
| radius | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully covers behavior: radius interpretation, caching with 10-minute TTL, live recalculation of hours, and null handling for unknown hours. It discloses all behavioral traits beyond the basic function.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured with purpose, usage, parameters, and return fields. Every sentence adds value; no redundant or extraneous text. Front-loaded the key purpose in the first sentence.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description completely documents all return fields with explanations, including edge cases like null values. All parameters are explained. The tool's behavior (caching, live hours) is fully covered.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, but the description provides detailed parameter semantics: lat/lng ranges, radius meaning with default and maximum, and concrete usage guidance. This goes far beyond the schema's minimal type information.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The first sentence clearly states the tool identifies a place from GPS coordinates and returns label, category, and live opening-hours status. The verb 'identify' combined with the resource 'place' and specific outputs makes the purpose unmistakable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Use this whenever the user provides coordinates or asks what is at a location.' This direct instruction tells the agent exactly when to invoke the tool, leaving no ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.1get_location_labelScored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The single tool's purpose is clearly defined.
With only one tool, naming consistency is inherently perfect. The name 'get_location_label' follows a clear verb_noun pattern.
A single tool is at the low end of typical scope. It serves a focused purpose (geolocation labeling), but the server feels thin for a full MCP surface.
The tool provides rich detail (name, category, hours, distance) for its single operation. Lacks additional geolocation utilities like batch or address lookup, but core need is met.
Worldwide place search with coordinates (Open-Meteo) — paid per call (x402/credits), 1 tools
Nominatim MCP — wraps OpenStreetMap Nominatim geocoding API (free, no auth)
OpenTripMap MCP — wraps the OpenTripMap Places API (dev.opentripmap.org)
Geocoding, routing, isochrones, traffic, weather, and place search for AI agents. 19 MCP tools.