Skip to main content
Glama
Sign In
ArcGIS Location Services MCP Server

ArcGIS Location Services MCP Server

by lwsinclair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

reverse_geocode

Convert geographic coordinates (longitude,latitude) to a readable address.

Instructions

Convert geographic coordinates to an address.

Args:
    location: Location as "longitude,latitude" (e.g., "-79.3871,43.6426")
    outFields: Fields to include in the response (default: all fields)

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

Input Schema

NameRequiredDescriptionDefault
locationYes
outFieldsNo*

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only explains parameter format but omits details like error handling, rate limits, or output structure (e.g., address format). Fails to provide sufficient transparency beyond basic functionality.

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?

The description is extremely concise, with a clear purpose statement and parameter documentation. No wasted words; every sentence adds value. Front-loaded with action.

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 simple two-parameter tool with no output schema or annotations, the description is adequate but incomplete. It could describe expected output format, coordinate bounds, or error behavior to fully inform usage.

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

Parameters4/5

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

Schema coverage is 0%, but description adds meaning: location format as 'longitude,latitude' with example, and outFields as 'Fields to include in the response' with default all. This significantly clarifies parameter usage.

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 clearly states 'Convert geographic coordinates to an address,' specifying the verb and resource. It implicitly distinguishes from sibling 'geocode' which does the reverse operation. This is specific and informative.

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 implied by the tool's purpose: use when you have coordinates and need an address. No explicit when-to-use or when-not statements, nor reference to alternatives like 'geocode'. Lacks clear guidance for selection.

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