eo-mcp

Overview Schema Source Related Servers Discussions Admin

discover_eo_tools

Search and filter Earth observation tools by category or keyword to locate the right MCP server tool for your geospatial task.

Instructions

Search and progressively discover eo-mcp tools across categories. Implements the client-side progressive discovery pattern (search, inspect, execute) recommended for modern MCP clients (Claude Code, Codex, Cursor, Antigravity).

Categories:

'workflows': Ergonomic multi-step tools (assess_location_hazard, environmental_site_audit).
'core': Fundamental spatial discovery and geocoding.
'spectral': Optical band indices (NDVI, NDWI, NBR, EVI) and SAR backscatter.
'hazards': Wildfire, flood inundation, burn severity, coastal erosion.
'climate': Urban heat, drought, crop phenology, atmospheric emissions.
'maritime': Dark vessel tracking, radar detection, and AIS correlation.
'advanced': Custom geospatial Python script runner and CDSE downloads.

Args: category: Optional category name to filter tools. query: Optional search keyword to filter tool names and descriptions.

Returns: JSON string listing available tools, categories, descriptions, and active profile.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discover_eo_tools"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No
`category`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden. It discloses the tool's read-only discovery behavior, explains how query and category filters behave, and states that the return value is a JSON string listing tools, categories, descriptions, and the active profile. It does not discuss error cases or side effects, but this appears to be a safe search tool, so the gap is minor.

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: a one-sentence summary, a brief contextual note about progressive discovery, a category list, and an Args/Returns section. It is longer than necessary due to the category examples, but each part earns its place by making the tool's contents immediately understandable.

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 that an output schema exists and there are only two optional parameters, the description is complete enough for safe invocation: it explains the purpose, both parameters, the valid categories, and the response shape. It could mention behavior when no arguments are supplied, but the optional/default schema makes that reasonably clear.

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

Parameters5/5

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

Schema coverage is 0% and there are no enums, so the description must compensate. It does so thoroughly: 'category' is described as an optional category filter, 'query' is described as an optional keyword filter for tool names and descriptions, and the valid category values are enumerated. This gives the agent everything needed to use the parameters correctly.

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 starts with a specific verb and resource: 'Search and progressively discover eo-mcp tools across categories.' It clearly identifies what the tool does and differentiates it from the domain-specific sibling tools by positioning it as a discovery/metadata tool. The category list with tool examples further reinforces the tool's scope.

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 explains that this tool implements the client-side progressive discovery pattern (search, inspect, execute) recommended for MCP clients, which clearly signals when it should be used: as the first step before selecting and invoking domain tools. It does not explicitly name alternatives or state when not to use it, but the context is strong enough for an agent to infer correct usage.

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