Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar regulaciones publicadas en gob.ec

search_regulaciones
Read-only

Search Ecuadorian regulations published on gob.ec and retrieve Registro Oficial references. Query keywords like 'datos personales' or 'LOTAIP' to find relevant legal documents.

Instructions

Search or list regulations published on gob.ec, with Registro Oficial references when available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number when query is empty (1-based)
queryNoKeywords (e.g. "datos personales", "tránsito", "LOTAIP")
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 when query is empty (1-based)"
    • addedInput schema / properties / query / description
      Added value: +"Keywords (e.g. \"datos personales\", \"tránsito\", \"LOTAIP\")"
  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: -"search_regulacionesArguments"
    • removedOutput schema / title
      Removed value: -"search_regulacionesDictOutput"
  4. First observedv0.8.12

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds that results may include Registro Oficial references, which is useful return-value context, but it does not disclose pagination behavior, rate limits, or other operational traits beyond what annotations provide.

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?

The description is a single well-formed sentence with no wasted words, and the core action is front-loaded. Every clause contributes to the purpose.

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 simple three-parameter search tool with rich annotations and full schema coverage, the description provides adequate context: what it searches, where, and a hint about return content. It could be more complete by explaining pagination behavior or the default output format, but the essential information is present.

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 the schema fully documents page, query, and format. The description adds no parameter-level detail beyond what the schema already provides, making 3 the appropriate baseline.

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?

The description names a specific verb (Search or list) and resource (regulations published on gob.ec), and adds a scope detail about Registro Oficial references. It does not explicitly differentiate itself from the sibling get_regulacion_info, but the search/list framing implies a contrast with detail-retrieval tools.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention of when not to use it, and no named alternative such as get_regulacion_info. The description states what the tool does but leaves the agent to infer when it should be preferred over sibling tools.

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