Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar contribuyentes por razón social

search_sri_ruc
Read-only

Find Ecuadorian SRI taxpayers by partial business or trade name when the RUC is unknown, returning up to 100 matches for identification.

Instructions

Find SRI taxpayers by partial razón social or trade name (min 4 characters) when the RUC is unknown. SRI caps results at 100.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
razon_socialYesText to search (min 4 characters), e.g. "BANANERA"
max_resultadosNoHow many results to return with full detail (max 100)

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. Changed2 schema fields changedv0.12.0
    • changedInput schema / properties / max_resultados / description
      Previous value: -"Cuántos resultados con detalle completo devolver (máx 100)"New value: +"How many results to return with full detail (max 100)"
    • changedInput schema / properties / razon_social / description
      Previous value: -"Texto a buscar (mínimo 4 caracteres), ej."New value: +"Text to search (min 4 characters), e.g. \"BANANERA\""
  3. Changed3 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / max_resultados / description
      Added value: +"Cuántos resultados con detalle completo devolver (máx 100)"
    • addedInput schema / properties / razon_social / description
      Added value: +"Texto a buscar (mínimo 4 caracteres), ej."
  4. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / max_resultados / title
      Removed value: -"Max Resultados"
    • removedInput schema / properties / razon_social / title
      Removed value: -"Razon Social"
    • removedInput schema / title
      Removed value: -"search_sri_rucArguments"
    • removedOutput schema / title
      Removed value: -"search_sri_rucDictOutput"
  5. First observedv0.8.12

TDQS

A4.2/5.0
Behavior4/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 behavioral context by noting the SRI-side cap of 100 results and the minimum search length.

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 with no filler. The core search behavior and the RUC-unknown condition are front-loaded, followed by the result cap.

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 simple read-only search tool with full parameter descriptions and a low parameter count, the definition gives enough to invoke it correctly. It could mention what identifying fields are returned, but that is a minor omission given there is no output 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 description coverage is 100%, so the schema already documents all three parameters, including the min-4 rule, max-100 cap, and format enum. The description repeats the min length and cap but adds no syntax or format guidance beyond the schema.

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?

The description states a specific verb (Find) and resource (SRI taxpayers), names the searchable fields (partial razón social or trade name), and explicitly distinguishes the tool from RUC-based lookup by saying 'when the RUC is unknown'.

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?

It gives a clear usage condition: use when the RUC is unknown, with a minimum of 4 characters. The sibling get_sri_ruc_info is implied as the alternative when the RUC is known, but that routing is not stated explicitly.

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