Skip to main content
Glama
Ellweb3

uruguay-mcp

by Ellweb3

Related Servers

Alternatives to uruguay-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to search and retrieve metadata and data files from Peru's National Open Data Platform, and generate Jupyter notebooks for data analysis.
      3
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to search, explore, and query any CKAN open data portal through natural language, making public datasets accessible without requiring knowledge of the portal's API.
      20
      1,372 npm
      57
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Brussels Open Data datasets through natural language or direct tool calls, including search, metadata retrieval, and SQL-like queries.
      5 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to search and analyze Ukraine's national open-data portal (data.gov.ua) using natural language, with tools for finding datasets, inspecting metadata, and retrieving actual data.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search, read, and explore thousands of public datasets from Chile's open government data portal (datos.gob.cl) without requiring an API key.
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search, retrieve metadata, and query tabular resources from Latvia's Open Data portal (data.gov.lv) via CKAN.
      5 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: call_tool for invocation, discover_tools for natural language search, execute_batch for concurrent calls, list_modules for module overview, and plan_query for multi-step planning. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (call_tool, discover_tools, execute_batch, list_modules, plan_query). The naming is predictable and uniform.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a meta-tool that discovers and invokes other data tools. The number feels complete without being excessive.

    Completeness5/5

    The tool surface covers the full workflow: discovering tools (discover_tools), planning multi-step queries (plan_query), invoking individual tools (call_tool), batch execution (execute_batch), and listing available modules (list_modules). No obvious gaps for its stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues