GeoSpark

Geometry operation

spatial_operation

Read-onlyIdempotent

Compute a buffer (shape-preserving, metres), geodesic area or length, centroid or convex hull.

Returns the resulting geometry as GeoJSON with its measurements and units.

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": {
      "operation": "<operation>",
      "geometry": "<geometry>"
    },
    "name": "spatial_operation"
  }
}

Input Schema

Name	Required	Description
`geometry`	Yes	A GeoJSON geometry, e.g. {"type": "Point", "coordinates": [lon, lat]}
`radius_m`	No	Buffer radius in metres
`operation`	Yes	What to compute; buffer also needs radius_m

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 / operation / description
```
Added value: +"What to compute; buffer also needs radius_m"
```
First observedOct 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so safety is covered. The description adds genuine behavioural context beyond that: buffer is shape-preserving and metric, measurements are geodesic, and the result is returned as GeoJSON with units attached. It stops short of stating error behaviour for invalid geometries or what happens when radius_m is omitted for non-buffer operations.

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, operation list front-loaded, with the return contract second — no filler. Slightly terse for a six-keyword operation surface: the parenthetical "(shape-preserving, metres)" is compressed almost to notation.

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 an output schema present the return shape needn't be spelled out, and annotations carry the safety profile, so the description is close to sufficient for a 3-parameter, single-tool geometry utility. It omits only edge-case behaviour (invalid geometry, degenerate input, coordinate reference assumptions) that would matter for a spatial tool.

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%, so the schema already documents geometry, radius_m (metres, 0–100000) and the operation enum. The description reinforces the metres/geodesic semantics but adds no format or constraint detail the schema lacks, so the baseline 3 applies.

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 ("Compute") and enumerates the exact resource set (buffer, geodesic area/length, centroid, convex hull), matching the operation enum one-to-one. It does not, however, distinguish itself from plausible siblings such as calculate_distance or isochrone, which also touch geometric measurement.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative; an agent must infer from the operation list alone whether to call this or calculate_distance for a measurement. The only conditional (buffer requires radius_m) lives in the schema, not the description.

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.