Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Listar instituciones públicas de gob.ec

list_instituciones
Read-only

Search and list public institutions from Ecuador's gob.ec registry by name or keyword, returning their official IDs for use in open data applications.

Instructions

List or search public institutions registered on gob.ec, with their IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based, default: 1, only used without query)
queryNoOptional search term (e.g. "SRI", "salud", "rentas")
formatNotext summary (default) or json structured result.text

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. Changed3 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / page / description
      Added value: +"Page number (1-based, default: 1, only used without query)"
    • addedInput schema / properties / query / description
      Added value: +"Optional search term (e.g. \"SRI\", \"salud\", \"rentas\")"
  3. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"list_institucionesArguments"
    • removedOutput schema / title
      Removed value: -"list_institucionesDictOutput"
  4. First observedv0.8.12

TDQS

A3.5/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 safety and openness profile is covered. The description adds only the fact that IDs are returned, which is genuinely useful for chaining, but it says nothing about pagination limits, result caps, or the difference between the text and json formats.

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?

A single front-loaded sentence with no filler; the core resource and the returned identifier are stated immediately. It is efficient, though arguably too sparse to guide invocation on its own.

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 three-parameter, all-optional lookup with no output schema, the combination of the description, the fully documented schema, and clear read-only annotations gives the agent enough to call it correctly. The missing piece is pagination/result-size expectations for the list mode, which is a modest gap.

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% and each parameter is documented in the schema itself, including the page/query interaction and the format enum. The description adds no extra semantics, so the baseline 3 for a fully documented schema is correct.

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

Purpose4/5

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

States a specific verb pair (list/search) applied to a clearly bounded resource (public institutions registered on gob.ec) and notes the payload includes IDs. It does not name the sibling get_institucion_info, so the agent must infer that this is the discovery step preceding it.

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?

"List or search" implies two modes (browse vs. query), and the schema backs that with 'only used without query', but the description never states when to prefer one mode or when to move on to get_institucion_info after obtaining an ID. Usage is implied rather than prescribed.

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