Gods Eye Geospatial MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_data_sourcesC | List the open-licence geospatial data sources wrapped by Gods Eye. |
| situational_queryA | Plan a geospatial situational-awareness query. Pass natural-language 'query' plus bounding box (minLon,minLat,maxLon,maxLat) or 'aoi_name' (an administrative area name). Returns a structured plan: which data sources to use, which products to fetch, how to chain them, and Care Membrane status. Actual tile fetching is a Pro-tier feature. |
| check_data_provenanceA | Given a geospatial stack description, flag proprietary / closed-licence dependencies and suggest open-licence, EU/UK-hosted alternatives. Useful for civilian projects with GDPR, data-residency, or open-data mandates (environmental NGOs, municipalities, research groups, CSRD reporters, agriculture co-ops). |
| care_membrane_policyC | Return the Care Membrane policy governing what Gods Eye will and will not do. |
| sign_data_provenance_attestationA | Generate a cryptographically signed data-provenance attestation for your geospatial stack (Pro/Enterprise). Produces HMAC-SHA256 signed JSON + public verify URL + optional board-ready PDF. Useful for CSRD E3/E4 evidence packs, GDPR Article 30 processing records, and municipal open-data mandates. Your auditor or procurement team validates the verify_url without needing to reach our backend.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool serves a clearly distinct purpose: policy retrieval, provenance checking, data source listing, attestation signing, and query planning. No overlap in functionality.
Naming patterns are inconsistent: 'care_membrane_policy' is a noun phrase, while 'check_data_provenance' and 'list_data_sources' follow verb_noun, but 'sign_data_provenance_attestation' is verbose, and 'situational_query' is adjective_noun. No consistent convention.
With 5 tools, the server is well-scoped for its focus on geospatial data provenance and situational awareness. Each tool adds distinct value without unnecessary bloat.
The tool set covers core workflows: listing sources, checking provenance, signing attestations, and planning queries. Minor gaps exist (e.g., no tool to fetch actual tile data, but that's a Pro feature), but for the stated purpose it is largely complete.