agrisignal-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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocode_locationA | Resolve a free-text place name to ranked latitude/longitude matches. Required first step before using the other tools, which take coordinates rather than place names. |
| get_soil_profileA | Fetch soil texture, pH, organic carbon, and water-holding properties for a coordinate from SoilGrids (ISRIC's global 250m-resolution soil map), at multiple depths. |
| get_growing_conditionsA | Snapshot of current weather, recent soil temperature/moisture readings, and a short daily forecast for a location — a general-purpose 'what's happening at this field right now' summary. |
| get_irrigation_adviceA | Estimate whether irrigation is needed by combining soil water-holding capacity (SoilGrids), current soil moisture, and the forecast balance of precipitation vs. reference evapotranspiration (Open-Meteo). Returns a data-grounded estimate with all inputs shown, not a certified recommendation. |
| get_frost_and_heat_riskA | Scan the daily forecast for temperature extremes that threaten crops: frost/freeze risk (low temperatures) and heat stress risk (high temperatures). Flags each day with any risk found. |
| get_growing_degree_daysA | Calculate accumulated growing degree days (GDD) over a date range using the modified method (floors Tmin at the base temperature, optionally caps Tmax). GDD tracks crop heat accumulation and is commonly used to predict development stage, maturity, and pest/disease emergence windows. Supports past dates (via historical reanalysis) and future dates (via forecast, up to 16 days out). |
| get_dry_spell_statusB | Check how many consecutive dry days a location has had and total precipitation over a lookback window, as a rough drought-risk indicator. Severity thresholds are a general rule of thumb, not a calibrated meteorological drought index. |
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 7 tools
Each tool targets a distinct agricultural or weather-related function: geocoding, dry spell, frost/heat risk, general conditions, GDD, irrigation advice, and soil profile. There is no overlap in purpose; the descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case, primarily using 'get_' or 'geocode_' as verbs. This makes the tool surface predictable and easy to navigate.
With 7 tools, the set is well-scoped for an agricultural signal MCP server. Each tool addresses a key aspect of agronomic decision-making without being overly numerous or sparse.
The tool set covers the core workflow: location resolution, drought, frost/heat, general conditions, GDD, irrigation, and soil data. A minor gap is the lack of a tool for direct crop stage prediction, but GDD provides a foundation for that.