uruguay-mcp
Related Servers
Alternatives to uruguay-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to search and retrieve metadata and data files from Peru's National Open Data Platform, and generate Jupyter notebooks for data analysis.5Apache 2.0
- AlicenseAqualityAmaintenanceEnables 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.201,614 npm59MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying Brussels Open Data datasets through natural language or direct tool calls, including search, metadata retrieval, and SQL-like queries.253 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to retrieve Peruvian public data behind one interface, including BCRP exchange rates and statistical series, state procurement records in the Open Contracting standard, and official gazette norms with search and detail tools.MIT
- AlicenseAqualityBmaintenanceEnables 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.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.8 npm1MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.