GeoSpark

Geocode a place

geocode

Read-onlyIdempotent

Find coordinates for an address or place name (OpenStreetMap Nominatim).

    Check `geospark.warnings` for ambiguous names (e.g. "Springfield") and ask the user
    which one they mean, or add a region.

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": {
      "query": "<query>"
    },
    "name": "geocode"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of matches to return
`query`	Yes	Address or place name

Output Schema

Name	Required	Default
`bbox`	No
`type`	No	FeatureCollection
`features`	Yes
`geospark`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Maximum number of matches to return"
```
First observedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the bar is lower. The description adds real value by disclosing the ambiguity failure mode and pointing at the geospark.warnings output path, which tells the agent how to detect and resolve disambiguation.

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 short sentences, front-loaded with the core action, no filler. The indented multi-line formatting is slightly awkward but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the description covers the main ambiguity pitfall. Minor gaps remain: no note on rate limits or provider policies and no explanation of what the limit default implies.

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% for both parameters, so the schema already carries the semantics of query and limit. The description adds no extra meaning about query syntax, limit behavior, or how region can be embedded in the query.

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?

States a specific verb and resource ('Find coordinates for an address or place name') and names the underlying service (OpenStreetMap Nominatim). This makes the forward-geocoding direction clear enough to distinguish it from reverse_geocode even though that sibling is not named.

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?

Gives concrete handling guidance for ambiguous results (check geospark.warnings, ask the user, add a region), which is genuinely useful. However it offers no guidance on when to pick this over reverse_geocode or other location tools, and 'add a region' is confusing since the schema exposes no region parameter.

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

All GeoSpark 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.