Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar auditores externos autorizados

search_auditores
Read-only

Search Supercías' registry of authorized external auditors by name or ID, with province filters and pagination, to verify credentials or find auditor records in Ecuador.

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)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
  3. 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 readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context that the corpus is a fixed registry of ~1,447 auditors, but says nothing about pagination behavior, result completeness, or rate limits beyond what the schema offers.

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 that identifies resource, source registry, corpus size, and accepted search keys with no 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?

With an output schema present and 100% schema coverage across five optional params, the description need not explain return values or pagination syntax. It is nearly complete; only a hint about alternative lookup tools would improve it.

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 every parameter (limit, query, format, offset, provincia) is already documented with defaults, enum, and matching semantics. The description's 'by name or ID' only restates the query param, adding no meaning beyond the schema. 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) plus resource (Supercías' registry of authorized external auditors) and adds scope detail (1,447 records, searchable by name or ID). This clearly distinguishes it from generic siblings like search_companias or search_organizations.

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?

Usage is implied by the search semantics, but there is no explicit guidance on when to prefer this over the sibling get_auditor_info, nor any note about prerequisites or when results are incomplete. Adequate but leaves routing to inference.

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