Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar auditores externos autorizados

search_auditores
Read-only

Search Ecuador's Supercías registry of authorized external auditors by name or ID; filter results by province and paginate through matches.

Instructions

Search Supercías' registry of 1,447 authorized external auditors by name or ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 20, max 100)
queryNoFree text matched against auditor name or identificación (RUC/cédula), accent-insensitive
formatNotext summary (default) or json structured result.text
offsetNoPagination offset over the matched set
provinciaNoOptional province filter, e.g. "PICHINCHA" (substring match)

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. Changed5 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / limit / description
      Added value: +"Max results (default 20, max 100)"
    • addedInput schema / properties / offset / description
      Added value: +"Pagination offset over the matched set"
    • addedInput schema / properties / provincia / description
      Added value: +"Optional province filter, e.g. \"PICHINCHA\" (substring match)"
    • addedInput schema / properties / query / description
      Added value: +"Free text matched against auditor name or identificación (RUC/cédula), accent-insensitive"
  3. Changed7 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / provincia / title
      Removed value: -"Provincia"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_auditoresArguments"
    • removedOutput schema / title
      Removed value: -"search_auditoresDictOutput"
  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 read-only, non-destructive, open-world behavior, so the bar is lower. The description adds that the registry is a fixed count (1,447) and search is by name or ID, but says nothing about match behavior, pagination, or rate limits beyond what the schema covers.

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?

A single front-loaded sentence of about 15 words with no filler. Every clause earns its place by naming the source, scope, and lookup keys.

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 full schema coverage and no output schema, the description covers purpose and scope adequately. Minor gaps remain around matching behavior and result format, but the schema carries most of the load.

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 already documents all five parameters including accent-insensitive matching and the province substring filter. The description repeats only the name/ID matching idea already in the schema, adding no new parameter semantics. Baseline 3 applies.

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 (Search), resource (Supercías' registry of authorized external auditors), and scope (by name or ID), with the registry size as context. It is clearly distinguishable from siblings like get_auditor_info (detail lookup) and search_companias (different registry).

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

Usage Guidelines3/5

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

The 'by name or ID' phrasing implies a lookup use case, but there is no explicit when-to-use vs get_auditor_info or when-not-to-use guidance. Usage is only implied.

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