GeoRescue MCP Server
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_datasetB | Inspect a parcel dataset (read-only). Filter issues by check name(s) and severity(ies), page with limit/offset, and set include_wkt to get each issue's geometry (working CRS WKT). |
| repair_datasetA | Write a repaired COPY of the dataset plus changelog into a NEW folder (a proposal output). Never modifies the input; refuses an out_dir that is the input's folder or already contains files. |
| list_tablesA | List tables in the GeoRescue results store (latest run, owner names redacted). |
| describe_tableC | Columns and types of a results-store table, e.g. 'issues' or 'cases'. |
| run_queryA | Run ONE read-only SELECT/WITH query on the results store. Capped (default 100, max 500 rows), 10 s timeout. Quote the column "check" (a keyword). |
| list_metricsA | List governed metrics (name, label, unit, description, allowed group_by). |
| get_metricB | Compute a governed metric from semantic/metrics.yml. Returns rows, the SQL used and caveats. |
| get_caseA | One case file by case_id (e.g. '0015420010__0015315300') or by a parcel ID (e.g. '001542 0010'): the proposed verdict, confidence, ORB refs, deed check (closure, IoU) and the parcel's issues. |
| find_issuesB | Filter issues in the latest run. bbox = [min_lon, min_lat, max_lon, max_lat] (EPSG:4326). Returns the total
match count and up to |
| explain_issueA | Plain-English explanation of an issue type or site term (e.g. 'sliver_polygon', 'closure', 'iou'), with the detection thresholds used, the automatic action and typical causes. |
| compare_runsB | Compare issue counts by check between two runs (default: the two most recent in the runs table). |
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 11 tools
Most tools target distinct resources or actions, and descriptions clarify boundaries such as inspect_dataset for parcel datasets versus find_issues for latest-run issues. Minor overlap remains between inspect_dataset and find_issues, and between run_query and governed metric tools, but the intended use cases are separable.
All tools use snake_case verb_noun names with clear, predictable verbs such as list_, get_, find_, inspect_, repair_, and compare_. Singular/plural noun choices are appropriate to each operation and remain consistent throughout.
Eleven tools is well scoped for a dataset inspection, repair-proposal, results-querying, metrics, and case-review server. Each tool covers a meaningful operation without obvious redundancy.
The surface covers inspection, repair proposal generation, results-store discovery/querying, governed metrics, case lookup, issue filtering/explanation, and run comparison. Minor gaps exist around listing cases or runs directly and applying a repair, but core workflows are supported.