Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Reverse Geocode

ReverseGeocode
Read-only

Reverse Geocode: Reverse Geocode converts latitude and longitude coordinates into US and Canada location details. Pass geographic coordinates to retrieve the corresponding city, state, postal code, and country code. (Cost: 6 credits)

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>",
      "lon": "<lon>"
    },
    "name": "ReverseGeocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesThe latitude of the coordinates
lonYesThe longitude of the coordinates

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely new behavioral context beyond that: the coverage is restricted to US and Canada, and each call costs 6 credits — both material to an agent's planning.

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?

Two sentences, front-loaded with purpose and then the returned fields and cost — all of which earn their place. The only waste is the redundant title echo in 'Reverse Geocode: Reverse Geocode converts...'.

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

Completeness4/5

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

With only two required scalars, a full output schema, and rich annotations, the description covers what an agent needs: input direction, output fields, region limits, and cost. The one meaningful gap is what happens for coordinates outside US/Canada (error vs. empty result), which is left unstated.

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%, with both lat and lon documented plus examples, so the schema carries the parameter burden. The description only restates that geographic coordinates are passed and adds no format, range, or precision guidance beyond that baseline.

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 and resource — converting latitude/longitude into US and Canada location details — and enumerates the returned fields (city, state, postal code, country code). The coordinate-in/address-out directionality and the explicit geographic scope make it distinguishable from address- or zip-input siblings such as CitiesLookup and ZipCodesLookup.

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: pass coordinates to obtain an address. The disclosed 6-credit cost and the US/Canada limitation give useful context for choosing this tool over free or global alternatives, but no sibling alternative is named and no explicit when-not-to-use condition is stated.

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

All APIVerve toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources