Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar división político-administrativa del Ecuador

lookup_ubicacion
Read-only

Look up Ecuador's provinces, cantons, and parroquias with INEC codes, region, and population, filtering parroquias by canton or province.

Instructions

Look up Ecuador's provinces, cantons and parroquias (rural and urban) with INEC codes, region and population. For parroquias, filter by canton and/or provincia.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nivelNoauto | provincia | canton | parroquiaauto
queryNoName or code (e.g. "Pichincha", "Cuenca", "Tumbaco", "170150")
cantonNoOptional canton filter (useful for parroquias)
formatNotext summary (default) or json structured result.text
regionNoOptional natural region for provinces/cantons
provinciaNoOptional province filter

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. Changed6 schema fields changedv0.10.0
    • addedInput schema / properties / canton / description
      Added value: +"Optional canton filter (useful for parroquias)"
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / nivel / description
      Added value: +"auto | provincia | canton | parroquia"
    • addedInput schema / properties / provincia / description
      Added value: +"Optional province filter"
    • addedInput schema / properties / query / description
      Added value: +"Name or code (e.g. \"Pichincha\", \"Cuenca\", \"Tumbaco\", \"170150\")"
    • addedInput schema / properties / region / description
      Added value: +"Optional natural region for provinces/cantons"
  3. Changed8 schema fields changedv0.8.14
    • removedInput schema / properties / canton / title
      Removed value: -"Canton"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / nivel / title
      Removed value: -"Nivel"
    • removedInput schema / properties / provincia / title
      Removed value: -"Provincia"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / region / title
      Removed value: -"Region"
    • removedInput schema / title
      Removed value: -"lookup_ubicacionArguments"
    • removedOutput schema / title
      Removed value: -"lookup_ubicacionDictOutput"
  4. First observedv0.8.12

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. Description adds that INEC codes, region, and population are returned and that parroquias can be filtered, but does not mention pagination, limits, or exact return shape.

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?

Two tight sentences: first states the resource and fields, second states the filter rule. No redundancy or filler.

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?

Given six optional params, read-only annotations, and no output schema, the description is sufficient to call correctly. It could say more about default 'auto' behavior or text vs json, but those are already in the schema.

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 coverage is 100% and every parameter is described there, so the schema carries the detail. The description only reinforces the canton/provincia filters for parroquias; baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb (look up) and resource (Ecuador's provinces, cantons, parroquias, INEC codes, region, population). Clearly distinguishable from tax/company/dataset siblings; no other sibling handles political-administrative divisions.

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?

Explicitly says 'For parroquias, filter by canton and/or provincia', giving condition-level guidance. No when-not-use or named alternative, but the niche is clear enough that no other tool competes.

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