Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar capas de un geoportal (INAMHI o MAG)

search_capas_geo
Read-only

Search geospatial layers from Ecuador's INAMHI (rainfall, forecast) or MAG (agro zoning, land cover) geoportals, filtering by category or WFS attribute data.

Instructions

Search layers of a GeoServer geoportal: inamhi (rainfall normals and anomalies, WRF forecast grids, watersheds) or mag (agro zoning, land cover, agricultural censuses, rural cadastre, agroclimatic risk). solo_wfs=true keeps layers with attribute data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree text matched (accent-insensitive) against the layer's id, name, title or abstract.
formatNotext summary (default) or json structured result.text
fuenteYesinamhi or mag.
solo_wfsNoOnly return layers with WFS (attribute data).
categoriaNoOnly for fuente="mag": one of its 8 categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Addedv0.10.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safe/live-remote nature is covered structurally. The description adds only one behavioral fact — that solo_wfs=true keeps layers with attribute data — and says nothing about pagination, result caps or rate limits against the live GeoServer.

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

Conciseness5/5

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

Two sentences, no filler, with the resource and both source vocabularies front-loaded before the filtering behavior. Every clause carries information an agent can act on.

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?

With five parameters, full schema coverage, and annotations carrying the safety profile, the description covers selection adequately. The notable gap is the absence of an output schema and any hint of what a match looks like (fields returned), plus no pointer to the sibling that retrieves actual layer data.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by enriching the fuente enum with concrete content taxonomies for each portal, which the schema only labels 'inamhi or mag'. It restates solo_wfs, which the schema already explains.

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?

States a specific verb (search) and resource (layers of a GeoServer geoportal), and enumerates what each source contains (rainfall normals, WRF grids, watersheds for inamhi; agro zoning, land cover, cadastre for mag). This is enough to distinguish it from data-retrieval siblings like get_capa_geo_datos or generic searchers.

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

Usage Guidelines3/5

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

Usage is implied by 'search layers' and by the source enumeration, but the description never says when to reach for this versus get_capa_geo_datos (fetch a layer's data) or other sibling searchers. No exclusions or prerequisites are given.

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