Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar trámites gubernamentales en gob.ec

search_tramites
Read-only

Search Ecuadorian government procedures (trámites) by keywords and institution ID to find relevant results for SRI, IESS, Registro Civil, and other agencies.

Instructions

Search gob.ec government procedures (trámites). Pass institution_id (SRI=8, IESS=163, Registro Civil=23, ANT=48, Cancillería=6; others via list_instituciones) for relevant results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based, default: 1).
queryNoKeywords to filter results (e.g. "RUC", "inscripción RUC persona natural").
formatNotext summary (default) or json structured result.text
institution_idNoInstitution ID (strongly recommended for relevant results)

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. Changed4 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / institution_id / description
      Added value: +"Institution ID (strongly recommended for relevant results)"
    • addedInput schema / properties / page / description
      Added value: +"Page number (1-based, default: 1)."
    • addedInput schema / properties / query / description
      Added value: +"Keywords to filter results (e.g. \"RUC\", \"inscripción RUC persona natural\")."
  3. Changed6 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / institution_id / title
      Removed value: -"Institution Id"
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_tramitesArguments"
    • removedOutput schema / title
      Removed value: -"search_tramitesDictOutput"
  4. First observedv0.8.12

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered without the description. The description adds the useful behavioral note that omitting institution_id degrades result relevance. It says nothing about pagination limits or the text/json output distinction beyond the schema.

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?

Two sentences, front-loaded with the action and then the critical parameter guidance. The dense ID list is justified because it is non-derivable, though the parenthetical is heavy enough to slightly blunt readability.

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 search tool with no output schema and full schema coverage, the description supplies the essentials: what it searches, the key filter and its values, and the fallback for unknown IDs. It could note paging or what a result contains, but nothing blocks correct invocation.

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, but the description genuinely adds meaning by mapping institution_id values (SRI=8, IESS=163, Registro Civil=23, ANT=48, Cancillería=6) that the schema only calls 'Institution ID'. This is exactly the kind of lookup data an agent cannot derive from the structured fields alone.

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 and resource: 'Search gob.ec government procedures (trámites).' That clearly separates it from get_tramite_info, get_tramite_estadisticas and list_instituciones, which it even references as the source of other IDs. It stops short of a crisp one-line scope statement, but the intent is unmistakable.

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?

Gives a concrete usage condition: pass institution_id for relevant results, and consult list_instituciones when the institution isn't in the listed set. It routes the agent to a sibling tool by name. No explicit exclusions or 'when not to use', so it falls just short of a 5.

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