Skip to main content
Glama
rajshivang07

agro-weather-mcp

by rajshivang07
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
geocode_locationA

Find candidate places by name.

Returns up to count candidates, where count is 1 through 10. Latitude and longitude are degrees, elevation is metres, and timezone is an IANA name. This tool has no date input and resolves the range to the current date. Example: geocode_location("Davis", "US", 3).

get_growing_degree_daysA

Calculate accumulated growing degree days from daily temperatures.

Dates use ISO YYYY-MM-DD and the inclusive range is at most 366 days. Temperatures and base/cap are degrees Celsius. The modified-average method clamps Tmin and Tmax to the base and upper cap before averaging. Daily values are returned for ranges up to 31 days, otherwise weekly summaries. Past dates use ERA5 archive data and future dates use the forecast, merged when needed. Example: get_growing_degree_days(38.54, -121.74, "2025-04-01", "2025-04-30").

get_frost_riskA

Assess overnight frost risk for the next 1 to 16 forecast days.

threshold_c is degrees Celsius and days is a forecast horizon. A night is low risk when its minimum is above threshold minus 2 C, moderate when it is above threshold minus 5 C, and high at or below threshold minus 5 C. Any hours below threshold make risk at least low. The result includes per-night minimum temperature and hours below threshold, in the forecast timezone. Example: get_frost_risk(45.52, -122.68, 7, 0.0).

get_water_balanceA

Calculate precipitation minus reference evapotranspiration.

Dates use ISO YYYY-MM-DD, are inclusive, and span at most 366 days. Precipitation, ET0, and the resulting balance are millimetres. ET0 is et0_fao_evapotranspiration for a well-watered reference grass field. Results include total precipitation, total ET0, total balance, weekly breakdowns, and a plain-language dryness note. Past and future ranges are merged from archive and forecast data. Example: get_water_balance(52.52, 13.41, "2025-06-01", "2025-06-30").

get_soil_conditionsA

Summarize current and next-48-hour soil conditions.

Soil temperature is degrees Celsius and soil moisture is volumetric water content in m³/m³ at the available 0-7, 7-28, 28-100, and 100-255 cm depths. The forecast covers the current time through approximately 48 hours in the resolved timezone. The sowing note is a rough guide only: many crops prefer about 8-10 C at seed depth, but crop, soil, and local practice matter. Example: get_soil_conditions(42.36, -71.06).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool covers a clearly distinct agronomic concept: place lookup, growing degree days, frost risk, water balance, and soil conditions. There is virtually no overlap—the shared lat/lon/date signature is a consistent input convention, not a source of confusion, and the descriptions make each tool's specific output obvious.

Naming Consistency4/5

All names follow a clean verb_noun snake_case pattern (geocode_location, get_growing_degree_days, get_frost_risk, get_water_balance, get_soil_conditions). The only minor deviation is 'geocode_location' using a domain-specific verb 'geocode' instead of the otherwise dominant 'get_' prefix, but it is still readable and predictable.

Tool Count5/5

Five tools is a tight, well-scoped set for a focused agro-weather service, with each tool covering a distinct analytical need. Nothing feels redundant or missing at the count level; it sits comfortably in the ideal 3-15 range.

Completeness4/5

The surface covers geocoding plus the core agronomic analytics (GDD, frost, water balance, soil), giving a coherent lifecycle for planning decisions. However, there is no general-purpose raw weather forecast or daily temperature/precipitation retrieval tool, which agents might reasonably expect from an agro-weather server as a fallback.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources