ScorpTech x402 API

Geocode

geocode

Read-onlyIdempotent

Geocode an address or place name to latitude/longitude (US Census Geocoder for US street addresses, Photon/OpenStreetMap worldwide), or reverse-geocode lat/lon to an address (with US county/tract). Read-only. Price: $0.005 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/geocode

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "geocode"
  }
}

Input Schema

Name	Required	Description
`q`	No	Address or place for forward geocoding
`lat`	No	Latitude for reverse geocoding
`lon`	No	Longitude for reverse geocoding
`lang`	No	Photon result language; default "en"
`limit`	No	limit; default 3
`provider`	No	provider; default "auto"

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's value is the extra disclosure: per-call pricing ($0.005 USDC via x402/Solana), which provider serves which geography, and an equivalent HTTPS endpoint. It omits rate limits and failure/ambiguity behavior, so it is strong but not exhaustive.

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?

Front-loaded with the two modes, followed by short factual sentences on read-only, price, and endpoint. Dense but efficient; the first sentence is long and packs provider selection into a parenthetical, which is a minor readability cost.

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 no output schema, the description still indicates what comes back in each direction (lat/lon forward; address plus US county/tract for reverse). Pricing and endpoint are covered, but error handling, multi-result behavior (implied by limit default 3), and ambiguity fallback are not described.

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 100%, so the baseline is 3, but the description adds meaning the schema lacks: the provider enum values are explained in terms of coverage geography (census = US street addresses, photon = worldwide) rather than just repeated as a name list. It does not clarify lang/limit semantics beyond the schema.

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?

States a specific verb and resource with both directions spelled out (forward geocoding address/place name to lat/lon, reverse geocoding lat/lon to an address) plus the backing providers. An agent can distinguish it from nearby siblings like census_geographies or timezone_convert without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the forward-vs-reverse selection explicit and explains the provider routing condition (Census for US street addresses, Photon worldwide). It does not name a sibling alternative or state when not to use it, so it falls short of the top score.

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

All ScorpTech x402 API tools Inspect

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

Need Help?