Skip to main content
Glama
xmpuspus

ph-civic-data-mcp

by xmpuspus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

MODIS vegetation index at a point

get_vegetation_index
Read-onlyIdempotent

Retrieve NDVI and EVI vegetation indices for any coordinate from NASA MODIS to monitor crop health, track deforestation, or assess drought conditions over custom date ranges.

Instructions

NASA MODIS MOD13Q1 NDVI and EVI vegetation index at any coordinate.

NDVI (Normalized Difference Vegetation Index) ranges -1 to 1. Higher values indicate denser healthy vegetation. EVI is more sensitive in high-biomass areas. The composite period is 16 days at 250m resolution. Useful for farm monitoring, deforestation tracking, and drought checks. Examples:

get_vegetation_index(15.58, 121.0) # last ~90 days at a point in Isabela get_vegetation_index(15.58, 121.0, "2026-08-01", "2026-08-15") # a fixed 15-day window

On failure: both MODIS bands failing returns data_status "unavailable", upstream_error true, samples [], and both band errors in caveats. One band failing still returns the other band's samples, but data_status stays "unavailable" with upstream_error true. A band whose rows carry no numeric value counts as that band failing. A pixel with no composite in range, such as one over water, is a real success with samples []. A latitude or longitude out of range returns data_status "invalid_request", with validation_error true and samples []. A start_date or end_date that does not parse as YYYY-MM-DD, or a span over 366 days, also returns data_status "invalid_request", checked before any fetch.

Input Schema

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

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 / start_date / description
      Previous value: -"ISO date (YYYY-MM-DD). Defaults to ~90 days ago."New value: +"ISO date (YYYY-MM-DD). Defaults to ~90 days ago. The\n        span from start_date to end_date cannot exceed 366 days."
  2. Addedv0.4.0

TDQS

A4.4/5.0
Behavior5/5

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

The description thoroughly explains edge cases: successful empty results over water, partial MODIS band failures, invalid-request handling, and date span limits. This goes well beyond the basic annotations and gives an agent a precise mental model of the tool's behavior.

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 detailed yet structured, with examples and explicit failure-mode statements that each add value. It is slightly verbose, but the richness of edge-case information justifies the length.

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

Completeness5/5

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

Given the output schema and annotations, the description covers input validation, output behavior for successes and failures, and partial-failure handling. No significant gaps remain for an agent to safely invoke and interpret the tool's results.

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 all parameter descriptions, including units, date format, defaults, and the 366-day span limit. The description adds examples and failure explanations but introduces no new parameter-level semantics 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 identifies the tool as retrieving NASA MODIS MOD13Q1 NDVI and EVI vegetation index values at a coordinate. It also distinguishes the tool by stating common use cases like farm monitoring, deforestation tracking, and drought checks.

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 gives concrete examples and lists typical use cases, providing clear context for when the tool is appropriate. It does not explicitly contrast alternatives among the many sibling tools, but the examples are sufficient to imply when to use it.

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