Find your next source.

Useful for

Use cases llm-inferred

Convert site addresses to coordinates for a desk-based constraints screen · Reverse-geocode survey or monitoring point coordinates to nearest address or locality for report labelling · Quick place-name lookup to confirm the county or district of a study area during scoping

Audience llm-inferred

GIS analysts · environmental consultants · civils engineers · planners

Limitations

Constraints llm-inferred

Designed for small volumes of geocoding; bulk CSV or database work is better served by OpenCage CLI tools or direct API calls · Requires Node.js 20 or higher and a local clone, npm install and build · Desktop config needs an absolute path to the built server file · Setup examples target the claude.ai desktop client; other MCP clients may need different configuration · Rate limits apply to accounts with hard limits; subscription accounts have no hard usage limits · First use requires the user to grant permission in the client

Example tool calls docs-verified

{
  "tool": "geocode-forward",
  "arguments": {
    "query": "Trafalgar Square, London",
    "countrycode": "gb",
    "limit": 1
  }
}

{
  "tool": "geocode-reverse",
  "arguments": {
    "latitude": 51.508,
    "longitude": -0.1281
  }
}

{
  "tool": "get-opencage-info",
  "arguments": {}
}

Useful for

Use cases llm-inferred

Site context mapping: geocode project addresses and map nearby OSM features (watercourses, schools, parking) for a site walkover pack · Travel planning for site visits: route_fetch and get_route_directions between office and client sites · Distance screening: geo_distance and sort_by_distance to rank candidate sites or monitoring locations by proximity to a reference point

Audience llm-inferred

GIS analysts · planners · environmental consultants · civils engineers needing site context

Limitations

Constraints llm-inferred

Rate limits apply: DOCS give defaults of Nominatim 1 rps, Overpass 2 per min, OSRM 100 per min, adjustable by flags · Data is OpenStreetMap-based; completeness and currency of tags are not described in DOCS · No UK-specific datasets, coverage statements or UK data sources are described in DOCS · Local install required: download a binary or build from source (Go 1.24+) · No hydrological, flood, drainage or ground data offered; not a substitute for authoritative UK datasets · Source of price data used by analyze_neighborhood is not described in DOCS · Coverage is inferred from ENTRY regions, not stated in DOCS

Useful for

Use cases llm-inferred

Zonal slope, aspect and elevation statistics over a site boundary from a DEM (geo-terrain dem_zonal) for drainage or civils options appraisal · Reproject and validate site boundary and survey vectors (geo-ops CRS transforms, geometry validation) before exchange with clients · Summer Sentinel-2 scene search over a site bbox (geo-stac) for pre-development land cover context · Species occurrence and OSM feature pulls (geo-biodiversity, geo-vector) as inputs to an ecological desk-study baseline

Audience llm-inferred

GIS analysts · geospatial developers · hydrologists · ecologists

Limitations

Constraints docs-verified

Foundation-model embeddings use a stand-in backend by default; real weights need a configured backend · Credentialed servers (geo-warehouse, geo-commercial-imagery, NOAA CDO, IUCN Red List) need API or cloud credentials · ERA5 is reached via the Open-Meteo archive, not a direct CDS client · Copernicus CLMS covers land-monitoring products, not raw Sentinel · Heavy compute depends on the separate aws-geo-compute peer Power and an AWS account · Without the [pdal] extra, point-cloud output is a local container and not interoperable COPC · Repository is named sample-*, so treat it as a reference implementation and assess maintenance risk

Useful for

Use cases llm-inferred

ERA5 rainfall and temperature history (weather_archive) for FRA or drainage baseline climatology · Forecast rainfall and wind for construction-phase site planning · GloFAS river discharge screening (flood_forecast) at site coordinates before gauge data review · CMIP6 climate projections (climate_projection) for climate-change allowances in drainage strategy

Audience llm-inferred

flood consultants · drainage engineers · hydrologists · planners · GIS analysts

Limitations

Constraints llm-inferred

Docs cover free use for non-commercial purposes only; commercial consultancy use must be checked against Open-Meteo terms · ENTRY auth lists API_KEY, but the docs say no key is needed for Open-Meteo; API_KEY only protects HTTP mode · Model-specific tools are regional (ICON for Germany/Europe, MET Norway for Nordic countries); UK coverage is not named · GloFAS flood discharge is modelled, not gauge observations · Responses over 25,000 characters are truncated; narrow the date range or variables to get full data · Response cache is in-memory only and not persistent · Archive ranges ending within the last 5 days are still being backfilled by Open-Meteo · Tool argument names in example_tool_calls are inferred from Open-Meteo API conventions, not from DOCS · Docs give no maintenance or release-status information

Useful for

Use cases llm-inferred

Tide and surge-context review for coastal flood risk assessment at US comparison sites · Sea level trend and 2022 SLR projection inputs for coastal climate-resilience appraisal (US sites) · Tidal datum (MLLW, MSL, NAVD88) and harmonic constituent checks for estuary or outfall modelling (US stations) · Marine wind and wave briefing for coastal works programme planning (US waters)

Audience llm-inferred

flood consultants · coastal engineers · hydrologists · marine civils engineers · planners

Limitations

Constraints llm-inferred

Great Lakes stations have no tide predictions · Subordinate (S) prediction stations only support hilo predictions · Predictions are astronomical; storm surge is not included · Per-product request-span limits are enforced client-side (e.g. 4 days for 1-minute data) · Oversized results return a response_too_large error rather than truncated data · NWS forecasts are limited to US lat/lon, up to about 7 days · No UK station coverage is stated; the NOAA network is US-centred · Tool argument names are not documented in DOCS; verify against the tool schema

Useful for

Use cases llm-inferred

Reference pattern for grounding AI assistant answers in 3D site or catchment context in a CesiumJS viewer · Prototyping AI-assisted camera control and 3D Tiles/terrain review for planning or drainage schemes · Agent-skill-driven CesiumJS code generation for internal geospatial visualisation tools

Audience llm-inferred

GIS analysts · web developers building CesiumJS apps · BIM and civils engineers reviewing 3D models

Limitations

Constraints docs-verified

Repository is deprecated; active development has moved to cesiumjs-ai-starter-app and cesiumjs-skills · Legacy architecture used a WebSocket bridge needing a separate local server process per user, tied to a single browser tab, and not scalable · No UK-specific or consultancy datasets; coverage is global and it provides integration patterns rather than data

Useful for

Use cases llm-inferred

Re-running a shared capsule for a flood or drainage model after updated rainfall inputs · Releasing a versioned capsule or pipeline as a reproducible analysis record for a project deliverable · Managing data assets that hold survey or monitoring inputs for a civils or environmental study

Audience llm-inferred

hydrologists · drainage engineers · GIS analysts

Limitations

Constraints llm-inferred

Requires a Code Ocean platform account and access token · Tied to a specific Code Ocean deployment via CODEOCEAN_DOMAIN · Tested against a minimum Code Ocean platform API version; pin the package version to match the deployment · Local install needs uv and Python 3.10 or newer · Streamable HTTP refuses requests without a token · No environmental or UK geospatial datasets are described in the docs · No tool names are listed in the metadata or docs, so tool calls cannot be confirmed from this entry

Useful for

Use cases llm-inferred

Flood zone, permit and code-case screening for a site due-diligence note · Zoning, lot dimensions and municipal code text lookup for a pre-application brief · Tree-permit and roadway work-zone check before site clearance or access planning · Special-district (MUD/PID) and appraisal context for a development or drainage-authority brief

Audience llm-inferred

flood consultants · planners · civils engineers · GIS analysts

Limitations

Constraints llm-inferred

Austin, Texas and Travis, Williamson and Hays counties only; no UK data, so relevance to a UK consultancy is low, although the catalogue lists regions as Global · Early-stage project run by a single maintainer, so expect gaps and possible breaking changes · MLS data covers active and under-contract listings only, with no sold comps · Listings, neighbourhood and blog content depend on neuhausre.com and the Neuhaus VOW API · Socrata rate limits apply unless an app token is set · Commute tool uses demo routing servers with no real-time traffic · Catalogue auth field says an API key is required, but docs say no key is needed · Catalogue tool list does not match docs: docs state 43 tools and list austin_utility_providers, austin_relocation, austin_local_voices and austin_health, which are absent from the metadata, while the metadata lists health_check

Useful for

Use cases llm-inferred

Prioritise open Navisworks clashes before a coordination meeting · Collapse repeated clashes to root-cause groups for trade discussions · Compare issue status between successive federated model deliveries · Prepare coordination work packages with trade ownership and PDF report images

Audience llm-inferred

BIM coordinators · BIM/civils engineers · design coordination managers

Limitations

Constraints docs-verified

Live coordination requires Windows and a licensed Autodesk Navisworks Manage 2024, 2025 or 2026 · Engineering approval and edits remain with the project team · Movement alternatives use element bounds and must be checked against surrounding geometry and design constraints · Revit and Power BI handoff relies on separate Horizun MCP servers

Useful for

Use cases llm-inferred

Flood-zone constraint screening for a project area using fema_nfhl · Soil and farmland siting indicators for drainage or SuDS options using nrcs_soils · Species and critical-habitat screening for early ecological constraints using ipac · Composite constraints map of a project area for early site appraisal using map_composer

Audience llm-inferred

GIS analysts · flood consultants · ecologists · planners · civils and BIM engineers

Limitations

Constraints docs-verified

Screening and research aid only; does not make legal or agency determinations or replace agency or Tribal consultation · Does not guarantee that upstream datasets are complete or current · map_composer queries public GIS services at request time, so results depend on those services being available · census and epa_aqs return no data until their credentials are set

Example tool calls docs-verified

{
  "tool": "ipac",
  "arguments": {
    "roi": "<project-area geometry; parameter name not stated in DOCS>"
  }
}

Useful for

Use cases llm-inferred

Check which layers are loaded in an open ArcGIS Pro map before a desk-study analysis · Count features in a named layer (e.g. Buildings) to sense-check a constraints or asset dataset · Zoom the ArcGIS Pro map to a named layer during a site or model review

Audience llm-inferred

GIS analysts · drainage engineers · civils engineers using ArcGIS Pro · developers extending ArcGIS Pro with MCP tools

Limitations

Constraints llm-inferred

Requires ArcGIS Pro to be running on the same machine with the Add-In loaded, because the named pipe only exists in that session · Only four operations are documented; selectByAttribute, getCurrentExtent and exportLayer are listed as next steps, not implemented · pro.countFeatures returns 0 when the layer name is not found, which is indistinguishable from an empty layer · No retry or timeout logic for IPC is documented (listed as a next step) · Agent Mode needs Visual Studio 2022 17.14 or later · Presented as a sample project; containerised deployment is listed as a future step, not provided

Useful for

Use cases llm-inferred

Flood exposure screening for a French study zone using the risque_inondation recipe · Building density and land-cover baseline for a site in France · Coastal land-pressure analysis from DVF transactions for a French coastal scheme · Print-ready PDF maps and QField data-collection packages for site visits in France

Audience llm-inferred

GIS analysts · flood consultants · planners · hydrologists · civils engineers

Limitations

Constraints docs-verified

Catalogue is France-only (IGN and French national datasets); no UK data sources documented · Production-ready only for single-user local deployments; multi-user mode is beta · Requires Docker and a running QGIS Desktop instance · Default WORKSPACE_AUTH_MODE is permissive: unauthenticated non-loopback calls are served · ign_dem_altitudes is compute-only and not renderable · Jobs over 30 s should use async tools; restart_qgis_engine causes 5-15 s of unavailability · Developed at Cerema Méditerranée; long-term maintenance not documented

Useful for

Use cases llm-inferred

Flood exposure screening for a French site: run risque_inondation to get flood zones and building exposure · Field survey prep: export a QField-ready ZIP with an editable Observations layer for site visits · Land-cover and hydrography baseline for a study area using set_study_zone and smart_load

Audience llm-inferred

flood consultants · GIS analysts · planners · environmental consultants · hydrologists

Limitations

Constraints docs-verified

Production-ready only for single-user local deployments; multi-user mode is beta · Requires a Docker host (docker compose) · Datasets are French national sources (IGN, DVF); no UK-specific data is documented, so UK use is limited · ign_dem_altitudes is compute-only and not renderable · restart_qgis_engine causes 5-15 s of unavailability · Jobs expected to exceed 30 s should use async tools to avoid timeouts · skill://file-exchange (bridge_put/bridge_get) is pending implementation · Default WORKSPACE_AUTH_MODE is permissive: unauthenticated non-loopback calls are served

Useful for

Use cases llm-inferred

Client-site presentation: fly the globe to a project location from a natural-language prompt · Visualising a time-dynamic scene (CZML) for a catchment or asset presentation · Prototyping an LLM-driven 3D GIS viewer before wiring in own UK water or civils data

Audience llm-inferred

GIS analysts · software developers building LLM-driven 3D viewers

Limitations

Constraints llm-inferred

Starter template, not a data source: no datasets are bundled · Chat needs an LLM API key; without one only a plain viewer runs · Terrain and imagery quality depends on the optional Cesium Ion token · Requires Node.js ≥ 22 and npm ≥ 9 for local dev, or Docker · Catalogue kind is 'mcp', but the docs describe an MCP client bridge that consumes external servers; no MCP tools are listed in metadata · Metadata region is Global, with no UK-specific data or coverage described

Useful for

Use cases llm-inferred

Desk-based site context screening: geocode an address, buffer 1-2 km, then pull OSM features (e.g. waterways, buildings) for a constraints check · Preliminary civils or drainage gradient checks: elevation profile along a proposed route or corridor · Terrain screening: sample and zonal stats of a client-supplied GeoTIFF DEM over a site boundary · Drive-time accessibility isochrones for planning or appraisal reports (requires OpenRouteService key)

Audience llm-inferred

GIS analysts · planners · drainage engineers · civils engineers · environmental consultants

Limitations

Constraints docs-verified

Release status: PyPI provides v0.3.0; the v0.4.0 release candidate (newest provider and hardening work) is not yet released · Default public providers have usage policies: Nominatim max 1 request/second, OSRM demo server not for production, Overpass fair use · Isochrones require GEO_MCP_ORS_API_KEY, which is unset by default · Docs are inconsistent on tool count (44 in places, 42 in CLI output) · Roadmap items not yet available: Mapbox/Google geocoding, WebSockets, batch file processing, reproject/clip/mosaic · No UK-specific datasets or hydrological time-series (gauge levels, rainfall) documented · Raster and vector tools operate on local files supplied by the user; no bundled datasets documented

Example tool calls docs-verified

{
  "tool": "geocode",
  "arguments": {
    "query": "Brandenburg Gate, Berlin"
  }
}

{
  "tool": "buffer",
  "arguments": {
    "point": {
      "lat": 52.5163,
      "lon": 13.3777
    },
    "distance_m": 1000
  }
}

Useful for

Use cases llm-inferred

Serve PostGIS drainage or flood-model layers to QGIS and ArcGIS Pro via OGC API Features or GeoServices FeatureServer · Publish survey or site investigation layers as vector tiles for client web maps · Expose PostGIS asset or monitoring data to Power BI or Excel via OData for reporting

Audience llm-inferred

GIS analysts · GIS developers · IT and DevOps teams hosting spatial data

Limitations

Constraints docs-verified

Serves data only; users must load their own layers (PostGIS required, bring your own or use the bundled compose stack) · No versioned v* release tagged yet; nightly container image is the current route · Pro and Enterprise features (e.g. FeatureServer applyEdits, service imports, OIDC SSO) need a signed license · ImageServer, OGC API Coverages and WMTS are Preview · Esri client compatibility is limited to the published parity and certification matrices

Useful for

Use cases llm-inferred

Expose an internal Laravel-hosted data service to AI assistants as MCP tools for a project team · Wrap an existing client REST API that has an OpenAPI spec as MCP tools using make:swagger-mcp-tool · Serve project-specific lookups or calculations from a Laravel app to consultants' AI tooling over Streamable HTTP

Audience llm-inferred

PHP/Laravel developers · backend engineers building internal MCP integrations

Limitations

Constraints llm-inferred

Framework only: the docs describe no geospatial, hydrology or environmental datasets, so the 'gis' category tag is not supported by the docs · Streamable HTTP is the only transport in v2.0.0; SSE was removed from runtime, which conflicts with the SSE mention in the entry description · Requires PHP >= 8.2 and Laravel >= 9.x (Lumen optional), so it needs a full Laravel or Lumen app · v2.0.0 has breaking changes (route-driven setup, setServerInfo); v1.0.0 users must migrate · No authentication built in; the production example depends on app-level middleware · Bundled tools are examples (HelloWorldTool, VersionCheckTool), not data tools

Example tool calls docs-verified

{
  "tool": "greeting-tool",
  "arguments": {
    "name": "Alex"
  }
}

Useful for

Use cases llm-inferred

Canadian hydrometric flow and flood-risk context for a flood risk assessment on a Canadian site · Canadian climate and rainfall normals as inputs to drainage design on Canadian projects · Discovering Canadian open geospatial datasets (CKAN, ArcGIS Hub, WFS) for desk-based site baselines · Canadian exchange-rate or commodity price inputs for project costing

Audience llm-inferred

hydrologists · flood consultants · GIS analysts · environmental consultants working on Canadian projects

Limitations

Constraints llm-inferred

Canada-only data; no UK coverage, so of limited use for terramcp.earth's UK-focused work · Entry description states 266 tools, but DOCS state 295 tools · Depends on many upstream government APIs whose availability and rate limits are outside the server's control · Requires Python 3.12+ and uvx to run · No spatial or temporal resolution or update frequency documented

Useful for

Use cases llm-inferred

Air quality baseline (PM2.5, PM10, NO2) for an EIA or planning air-quality section · Rainfall, wind and temperature history over a date range to support site monitoring or construction-weather reporting · Current weather context for a site visit or field-survey log · Timezone-correct timestamp conversion for consultancy field records

Audience llm-inferred

environmental consultants · air quality specialists · drainage engineers · civils engineers · planners

Limitations

Constraints llm-inferred

Location is a city name in English only; no coordinate or site-level input is documented · Data is city-level, not site-specific, so not suitable for site-scale design inputs without validation · Depends on the third-party Open-Meteo API being available · SSE mode is described as legacy; streamable HTTP is the modern option · Not UK-focused in metadata (regions: Global); no UK-specific data sources or stated accuracy · No stated beta status, rate limits or SLA

Useful for

Use cases llm-inferred

Tide and surge levels at Dutch coastal sites for marine works or outfall boundary checks (tides_nl) · Wind and wave forecast windows for coastal survey or dredging campaign planning · Bridge clearance and fairway depth checks for barge or crane access routes (fairway_nl)

Audience llm-inferred

coastal and marine engineers · hydrologists · civils and BIM engineers planning marine logistics · GIS analysts

Limitations

Constraints llm-inferred

Built and documented for recreational sailing, not engineering or regulatory use · Official charts, almanacs and notices must be checked before relying on outputs · Windy, WorldTides, Stormglass and AISStream need user-supplied API keys; keyed tools only appear when the key is present · AISStream is community-fed and sparse mid-ocean · Some bridges may show '(name unknown)' where OSM has no nearby named bridge · All tool times are UTC · Depends on third-party public endpoints (RWS, NDW, OSM/Overpass, aviationweather.gov, Open-Meteo) with no stated SLA · No public hosted endpoint is documented; the user must run or host an instance (docs use a 'your-host' placeholder) · ENTRY metadata lists OAuth, but DOCS describe API-key URL parameters and state 'No OAuth required' for Claude.ai · Likely single-maintainer personal project ('Built by @ai_kulikov'), so maintenance risk

Useful for

Use cases llm-inferred

Cadastral and OEREB public-law restriction check for a Swiss parcel during site appraisal · Elevation profile along a candidate Swiss route or alignment for civils option appraisal · Contaminated-sites and hazard-map screening for a Swiss canton via geodienste.ch layers · Commune and BFS-number lookup to join Swiss project areas to BFS statistics

Audience llm-inferred

GIS analysts · civils engineers · planners · environmental consultants

Limitations

Constraints llm-inferred

Switzerland-only data; provides no UK coverage, so not applicable to UK projects · ENTRY metadata is inconsistent: it says 13 tools while the docs describe 20; its tool list includes output field names (summary, results, count, match_type, is_error), a parameter name (operation) and names not in the docs (swisstopo_feature_lookup, swisstopo_geodata_download); verify tool names against the running server · Version 0.5.0 per docs badge (pre-1.0): maintenance and API stability risk · Depends on external services (Swisstopo, geodienste.ch, Overpass, OpenPLZ); availability not guaranteed · Zoning result is not legally binding (per docs) · Hosted use in browser requires self-deploying the server (e.g. on Render); no hosted endpoint is documented · Time span and spatial/temporal resolution are not documented

Useful for

Use cases llm-inferred

Diagnose why a client's web application or portal was slow in a given window, using Tideways performance data · Triage errors and slow SQL in a client-hosted web app during handover or post-release review · Check a client web platform's request volume and p95 response times across a project's services

Audience llm-inferred

web application developers · DevOps and site reliability engineers maintaining Tideways-monitored applications

Limitations

Constraints llm-inferred

Not an environmental, hydrological, water or civils data source; it is application performance monitoring for web apps, so the 'environment' category in the entry does not match its content · Unofficial, community-maintained server, not affiliated with or supported by Tideways · Requires a Tideways account and API token; the token must have the metrics, traces and errors scopes · Rate limit is per Tideways organisation per clock hour and is shared by all of its tokens and projects; its size depends on the plan · History is available for production and the default service only · Issues are returned 10 per page · Performance data covers roughly the last 30 days · All times are UTC · Requires Node.js 22+ or Docker to run

Useful for

Use cases llm-inferred

Testing MCP streamable-HTTP client configuration against a live public server before wiring similar tools into a project · Evaluating agent-to-agent write and lineage APIs for a internal prototype (not a source of environmental or water data) · Reference example of an open MCP server with self-correcting error responses and rate-limited REST endpoints

Audience llm-inferred

MCP and AI agent developers · AI tooling evaluators

Limitations

Constraints llm-inferred

Not environmental, hydrological, geospatial or civils data; it is a public shared text space and nothing published to it is private · No geographic or temporal coverage or update schedule; regions 'Global' in the entry is not a data coverage statement · Rate-limited per IP; session limits of 7 imprints, 5 weaves and 15 witnesses; per-agent limits of 12 imprints and 20 weaves per hour · Entry kind is 'skill' but the project is an MCP server plus REST API; the tools array is empty in the entry metadata · Community-launched crypto tokens are referenced in the docs and are unrelated to the data or access model

Useful for

Use cases llm-inferred

Swiss project site screening using Zurich district and school-district boundary layers from the geoportal · Drainage and water context for Zurich-area reviews using Lake Zurich level and temperature and UGZ weather station data · Environmental baseline for Zurich assessments using live air quality (NO2, O3, PM10, PM2.5) and climate raster layers · Policy and stakeholder background using council resolutions and parliamentary motions

Audience llm-inferred

environmental consultants · planners · GIS analysts · hydrologists (Zurich-area projects)

Limitations

Constraints docs-verified

Covers City of Zurich data only; no UK coverage · SPARQL tool is not registered by default and its endpoint is not yet productive · Releases before 0.6.0 fail at import on mcp 2.x; use 0.6.0 or newer · HTTP transport has no built-in authentication; set MCP_ALLOWED_HOSTS when binding beyond loopback · Live feeds depend on upstream APIs (e.g. ParkenDD); no rate limits documented

Useful for

Use cases llm-inferred

Cut/fill earthwork volumes between existing ground and finished grade surfaces · Watershed delineation and Rational Method runoff checks for site drainage · Pipe network layout and hydraulic analysis for drainage design · Plan/profile sheet production and PDF publishing for design submissions

Audience llm-inferred

civil/highway design engineers · drainage engineers · hydrologists · BIM/civils engineers

Limitations

Constraints docs-verified

Requires a licensed local Civil 3D 2026 installation and Autodesk API references; Autodesk binaries are not shipped with the repo · Setup docs are Windows-focused (PowerShell commands, Civil 3D plugin built with .NET 8 on Windows) · The Civil 3D plugin must be loaded in a running Civil 3D session for drawing operations · Default MCP surface exposes 34 tools; the full 219-tool surface needs CIVIL3D_ENABLE_TOOL_ALIASES enabled · Entry lists 180 tools, which does not match the 34 public / 219 registered counts in the docs · Destructive or file-writing actions require the preview, approval-token, retry flow · Autodesk-hosted tutorial video playback requires internet access

Useful for

Use cases llm-inferred

Hydrology baseline from nearest Swiss gauging station (levels, flows) for water-resource projects · Air quality baseline check against Swiss LRV and WHO 2021 limits for EIA screening · Aircraft noise screening of planning sites using LV95 coordinates · Natural hazard screening (flood, avalanche, wildfire) in site due diligence

Audience llm-inferred

hydrologists · environmental consultants · planners · GIS analysts

Limitations

Constraints docs-verified

Swiss data only; not applicable to UK sites · Hydro station search has no canton filter; flood warnings are nationwide with no canton filter · env_hydro_history returns latest value plus an access path for real-time series, not full series · Aircraft noise contours are isolines: results are a dB bracket/upper bound, orientation aid only, not legally binding · Coordinates must be LV95 (EPSG:2056); WGS84 input is rejected · Hazard overview/regions tools are routers only; the naturgefahren.ch aggregate API was discontinued · Per-query caps apply and each API call times out after 30 seconds · Subject to upstream terms of service (BAFU, hydrodaten.admin.ch, naturgefahren.ch, waldbrandgefahr.ch) · Requires Python 3.11+ for local install · Tool budget is declared exhausted (21 tools); metadata lists tools as empty

Useful for

Use cases llm-inferred

FRA baseline flows from nearest gauge: find sites by bbox, then pull daily mean discharge (00060) for the baseline period · Current conditions check at gauges during a flood or drought review, using percentile ranking as indicative only · Groundwater depth baseline from monitoring wells via parameter 72019 · Monitoring site inventory for a catchment by HUC code, filtered to sites with instantaneous data

Audience llm-inferred

hydrologists · flood risk consultants · drainage engineers · GIS analysts · ecologists (groundwater and surface water baselines)

Limitations

Constraints llm-inferred

Covers US and territories only; no UK data · Percentile ranking is approximate and is not a flood-stage or drought determination · Readings return up to 100 sites per call, with at most 100 series and the 10 most recent records per series · Series inline output is capped at 500 records; larger results need CANVAS_PROVIDER_TYPE=duckdb · Dataframe tools and spillover require CANVAS_PROVIDER_TYPE=duckdb; table drop is opt-in via WATER_DATAFRAME_DROP_ENABLED · Pre-1.0 release (v0.3.0), so the interface may change · Relies on the USGS NWIS service being available; upstream failures are returned as retryable errors · Public hosted endpoint is not operated by USGS and has no stated uptime guarantee

Useful for

Use cases llm-inferred

Read-only audit of surfaces, alignments and COGO points with their layers before issuing a drawing · Scripted extraction of surface and alignment station/offset data for a drainage or highway design check · Batch creation of repetitive civils objects from skill templates in a design workflow

Audience llm-inferred

civils BIM engineers · drainage engineers · highway engineers · CAD technicians

Limitations

Constraints llm-inferred

Requires Autodesk Civil 3D to be running with the plugin loaded (NETLOAD, C3DMCPSTATUS to verify) · civil3d_execute modifies the drawing and commits the transaction · Roslyn sandbox blocks process execution, file deletion, network requests, registry access and dynamic assembly loading · Default execution timeout is 120000 ms · Argument names for the three tools are not documented in DOCS; the code parameter name in example_tool_calls is inferred · Code is AI-generated and runs with full Civil 3D API access, so output needs review before use on live drawings · Windows and Civil 3D version requirements are not stated in DOCS