Skip to main content
Glama

gisgp

by io.github.uponex

overlay_geojson

Combine two GeoJSON FeatureCollections with a boolean set operation.

op: intersection | difference (a minus b) | symmetric_difference | union.
Each side is unioned into one geometry first, then the operation is
applied. Returns JSON {ok, op, geojson} — empty geojson means no overlap,
not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opNointersection
geojson_aYes
geojson_bYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that each side is unioned first, the return format (JSON with ok, op, geojson), and that an empty geojson indicates no overlap, not an error. It lacks mention of side effects or authorization needs, but for a read-like analysis tool, the behavior is well-explained.

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 three sentences long, each adding value: purpose, operation details, and return format. It is front-loaded with the core action and very concise, with no wasted words.

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

Completeness5/5

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

Given the presence of an output schema (not shown but indicated), the description sufficiently covers return values and edge cases. Parameter explanations are clear, and the sibling context shows this is a geometric overlay tool among many others, so the description is complete for its complexity.

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

Parameters5/5

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

Schema coverage is 0% (no parameter descriptions), so the description must compensate. It explains the 'op' parameter with its four allowed values and default, and implies that geojson_a and geojson_b are the two input FeatureCollections. This adds significant meaning beyond the schema's bare titles and types.

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 the tool's purpose: 'Combine two GeoJSON FeatureCollections with a boolean set operation.' It lists the operations (intersection, difference, symmetric_difference, union) and explains the behavior (each side unioned first). This distinguishes it from sibling tools like buffer_geojson, dissolve_geojson, and spatial_join_geojson, which handle different geometric operations.

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?

The description implies use for boolean operations on geometries but does not explicitly state when to use this tool versus alternatives like buffer_geojson or dissolve_geojson. No clear context for when-not-to-use or specific prerequisites are provided.

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

All gisgp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation2/5

Many assess_* composite tools (datacenter, ev_charging, renewable, telecom, due_diligence) share the same building blocks of grid proximity, land cover, and terrain, making their boundaries fuzzy. assess_property_hazard_x402 also duplicates assess_property_hazard with only a payment-method difference, and bundle_* tools intentionally overlap with the free primitives they replace.

Naming Consistency3/5

There is a mix of verb_noun tools (query_features, geocode_address), noun-first geometry tools (centroids_geojson, envelope_geojson), and inconsistent _geojson suffix usage (buffer_geojson, fix_geometry, geometry_stats). The assess_* and bundle_* prefixes offer some grouping, but no single naming pattern is followed across the set.

Tool Count1/5

With 85 tools, the surface is extreme for an MCP server and far exceeds the typical well-scoped 3-15 range. Many tools are convenience bundles or variants that could be consolidated, making the count a significant usability burden.

Completeness4/5

The toolkit covers a broad range of GIS tasks: format conversions, GeoJSON analysis, FeatureServer query/inspection, geocoding, site assessment, and sharing. Minor gaps exist (e.g., no Excel-to-GeoJSON, no FeatureServer update/delete), but most missing functionality can be worked around by chaining existing tools.

Resources