Skip to main content
Glama
Sign In
snapp-mcp

snapp-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Describe coordinates

reverse_geocode
Read-onlyIdempotent

Convert latitude and longitude coordinates into readable place details such as point of interest, street, and neighbourhood.

Instructions

Describe coordinates in words (point of interest, street, neighbourhood).

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>",
      "long": "<long>"
    },
    "name": "reverse_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesDelivery latitude.
longYesDelivery longitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • changedInput schema / properties / lat / description
      Previous value: -"Delivery point latitude."New value: +"Delivery latitude."
    • changedInput schema / properties / long / description
      Previous value: -"Delivery point longitude."New value: +"Delivery longitude."
  2. Changed6 schema fields changedv0.2.0
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude of the delivery point (Iran: ~25 to ~40)."New value: +"Delivery point latitude."
    • removedInput schema / properties / lat / title
      Removed value: -"Lat"
    • changedInput schema / properties / long / description
      Previous value: -"Longitude of the delivery point (Iran: ~44 to ~63)."New value: +"Delivery point longitude."
    • removedInput schema / properties / long / title
      Removed value: -"Long"
    • removedInput schema / title
      Removed value: -"reverse_geocodeArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "reverse_geocodeDictOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and repeatability are covered. The description adds the useful behavioral fact that results come back as textual address levels rather than raw geometry, but it says nothing about lookup latency, failure behavior for out-of-region coordinates, or the coordinate reference system.

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?

A single front-loaded sentence with no filler, and the parenthetical neatly enumerates the levels of detail returned. Slightly redundant in saying "in words" immediately after "describe", but nothing is wasted.

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

Completeness3/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 full schema coverage and no output schema, the description covers the essentials. It stops short of stating the region implied by the tight lat/long bounds (24–40, 44–64) or what happens outside them, which is the main thing an agent could get wrong here.

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 parameters are documented ("Delivery latitude", "Delivery longitude") with explicit min/max bounds. The description adds no syntax, format, or coordinate-system detail beyond identifying the inputs as coordinates, so the schema is doing all the semantic work.

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 names a specific verb ("describe") and resource (coordinates), and clarifies the output granularity with examples (point of interest, street, neighbourhood). It is clear what the tool does, but it does not distinguish itself from the sibling find_location, which an agent could plausibly pick instead.

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 parenthetical output examples suggest this is for resolving raw lat/long into human-readable place descriptions. There is no explicit statement of when to prefer this over find_location, no prerequisites, and no note that the accepted coordinate range is a limited region.

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