cart-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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rate_aoiA | Rate an area of interest (WKT, EPSG:4326) for CART soil resource concerns. Submits the CART pipeline to the public Soil Data Access web service and returns
the landunit rating for every ratable concern (or the subset given in |
| rate_aoisA | Rate multiple landunits in one pipeline run.
|
| get_aoi_soil_summaryA | Map units and major components intersecting an AOI (no ratings). Returns per map unit: mukey, symbol/name, survey order (invesintens), farmland class, acres, and its major components (compname, comppct_r, drainage class). Useful for transparency (E4) and leaching/water-table screening (W4). |
| get_aoi_soil_mapA | Soil map for an AOI as GeoJSON (FeatureCollection). Each feature is a soil polygon clipped to the AOI with properties {landunit, mukey, musym, muname, invesintens, farmlndcl, poly_acres}. Render directly with Leaflet/ArcGIS; no ratings are computed. |
| get_aoi_risk_mapA | Risk map for one cointerp-backed concern as GeoJSON (FeatureCollection). Each feature is a soil polygon clipped to the AOI carrying the rating (rating_value, rating_class) of the dominant major soil component in its map unit. Order 5 survey map units are rated 'Not rated'. Supports cointerp-backed concerns only (e.g. the five SOH concerns, Hydric, Ponding/Flooding, AWS, Depth to Water Table, Drainage Class); SOC and other custom concerns raise an error. |
| list_concernsA | All CART resource concerns with pipeline type, data source, computability, and docs. |
| get_concern_detailsC | Full profile for one concern: domain, practices, regulatory references. |
| get_rating_domainB | Ordered rating classes (worst to best) for a concern. |
| list_practices_for_concernA | NRCS conservation practices that address a concern (advisory). Sourced from the public NRCS CART Practice Points spreadsheet ('Assoc Ag Land' points). Practices are listed by NRCS practice code, name, and points - they are suggestions for discussion, not a formal practice plan. |
| validate_pipelineA | Re-run the pipeline on the T9981 Fld3/Fld4 test fields and diff against golden values. Network required. Golden values are tied to the 2018 ND001/SD105 survey-area snapshots; a mismatch may be legitimate if those areas were republished since. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| rate_land_for_conservation | |
| validate_cart_pipeline |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_concerns_index | Index of all CART resource concerns. |
| resource_interpretations | Soil interpretation name mappings (attributename <-> mrulename <-> rulekey source). |
TDQS
Scored across 10 tools
The tools are largely distinct, but rate_aoi and rate_aois are essentially the same operation for one vs. multiple areas, and get_concern_details includes rating domain information that overlaps with get_rating_domain. Still, the descriptions make the intended use clear.
All tool names follow a consistent verb_noun pattern with clear prefixes (list_, get_, rate_, validate_). Pluralization and compound nouns are used predictably.
With 10 tools, the set is well-scoped for the CART/AOI analysis domain. Each tool serves a clear purpose without redundancy.
The server covers listing concerns, retrieving details and ratings, generating soil and risk maps, and validating the pipeline. A minor gap is that risk maps only support cointerp-backed concerns, but rate_aoi covers custom concerns, so the overall workflow is complete.