Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver muestra de datos de una capa de geoportal

get_capa_geo_datos
Read-only

Sample up to 20 attribute records from an Ecuadorian WFS layer to preview its data structure. Fetches non-spatial feature previews by source and layer, without bbox filters or geometry.

Instructions

Sample up to 20 features' attributes from a WFS-enabled layer (capa from search_capas_geo). A preview, not a spatial query: no bbox or filters, and geometry is dropped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
capaYesThe layer's `capa` from search_capas_geo (INAMHI: "geonode:..." name; MAG: "categoria/store/name").
countNoNumber of features to fetch (1-20, default 5).
formatNotext summary (default) or json structured result.text
fuenteYesinamhi or mag.

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.2/5.0
Behavior4/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 safety is covered. The description adds genuinely useful behavior beyond that: the 20-feature ceiling, absence of bbox/filter support, and the fact that geometry is dropped from results, which shapes expectations of the payload.

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 tight sentences with no filler, and the identifying information (what it samples, from where) comes first, with the scoping caveat immediately after.

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?

For a read-only preview tool with fully documented parameters and no output schema, the description supplies output-shape context (attributes only, geometry dropped) and the source of the required layer identifier. Nothing essential is missing, though the text/json format distinction could have been tied to expected output.

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?

Schema description coverage is 100%, so all four parameters (capa, count, format, fuente) are already documented with formats, defaults, ranges and enums. The description only echoes the 20-item cap and the capa provenance, adding little beyond structured data, so baseline 3 applies.

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 and resource: sampling feature attributes from a WFS-enabled layer, with the exact cap (20) named. It also routes the agent to the sibling that produces the required `capa` value (search_capas_geo) and explicitly carves itself away from a spatial query tool.

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 phrase 'A preview, not a spatial query' tells the agent when this tool fits and, by negation, when it does not. It also implies the prerequisite source of `capa`. It stops short of naming a concrete alternative tool for the spatial-query case, so it is clear context rather than a full when/when-not/alternative map.

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