Skip to main content
Glama
xmpuspus

ph-civic-data-mcp

by xmpuspus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Solar irradiance and climate at a point

get_solar_and_climate
Read-onlyIdempotent

Retrieve daily solar irradiance, temperature, precipitation, and wind speed for any coordinate to support solar-site screening, farm planning, and climate checks.

Instructions

Daily solar irradiance and climate variables from NASA POWER for any coordinate.

Returns daily solar irradiance, 2m temperature, corrected precipitation, and 2m wind speed, in kWh per m2, Celsius, mm, and m per second. Useful for solar-site screening, farm planning, and historical climate checks. Examples:

get_solar_and_climate(14.5995, 120.9842) # Manila, last 14 days get_solar_and_climate(14.5995, 120.9842, "2026-04-01", "2026-04-02") # a fixed 2-day window

On failure: an upstream fetch failure or a non-object response body returns data_status "unavailable", with upstream_error true, days [], and the real error text in caveats. A properties or parameter field that is missing, null, or not an object returns data_status "indeterminate", with upstream_error true and days []. A start_date or end_date that does not parse as YYYY-MM-DD, an end_date before start_date, a span over 366 days, or a latitude or longitude out of range, returns data_status "invalid_request", with validation_error true and days [].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateNoISO date string (YYYY-MM-DD). Defaults to today. The span from start_date to end_date cannot exceed 366 days.
latitudeYesDecimal degrees, WGS84.
longitudeYesDecimal degrees, WGS84.
start_dateNoISO date string (YYYY-MM-DD). Defaults to 14 days ago.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • changedInput schema / properties / end_date / description
      Previous value: -"ISO date string (YYYY-MM-DD). Defaults to today."New value: +"ISO date string (YYYY-MM-DD). Defaults to today. The span\n      from start_date to end_date cannot exceed 366 days."
  2. Addedv0.4.0

TDQS

A4.3/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly and idempotent hints in annotations, the description details data source, units, return variables, and comprehensive failure modes including specific data_status values for upstream errors, invalid dates, range violations, and malformed responses. This gives a full behavioral picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with purpose, return values, use cases, examples, and failure modes, but it is somewhat lengthy and repeats that daily solar irradiance and climate variables are returned. Overall it is appropriately detailed without being excessively verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and the description covers data source, units, typical use cases, examples, and detailed error behavior, the context is largely complete. It does not specify exact output fields, but the output schema and error descriptions fill that gap sufficiently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already covers parameter meanings with defaults, date span limits, and coordinate format, so the description adds limited new parameter-level semantics. It reinforces validation behavior regarding invalid dates and out-of-range coordinates, but does not define latitude/longitude ranges or add detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns daily solar irradiance and climate variables from NASA POWER for any coordinate, naming specific variables and units. It also identifies use cases like solar-site screening and farm planning, leaving no ambiguity about the tool's purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides concrete examples and notes general use cases, but does not explicitly guide when to choose this tool over closely related siblings like get_weather_forecast or get_flood_forecast. The examples and stated applications give enough practical direction for most agents.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools