Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Rankear compañías por indicadores financieros

search_ranking
Read-only

Rank Supercías companies by financial indicators or CIIU sector for a chosen fiscal year to identify top performers. Sort descending by columns like sales or ROE to get top-N rankings.

Instructions

Rank Supercías companies by financial indicators for one fiscal year (last five years), optionally by CIIU letter. descending=true for top-N by a column.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoFiscal year filter; defaults to the latest available year (the latest year may still be incomplete while filings arrive).
limitNoMax results (default 20, max 100).
formatNotext summary (default) or json structured result.text
offsetNoPagination offset.
ciiu_n1NoOptional CIIU level-1 filter, e.g. "C", "G", "I".
order_byNoColumn to sort by (e.g. "posicion_general", "activos", "roe").posicion_general
descendingNoSet true for "top N" style queries (e.g. highest ingresos_ventas/roe first).

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. Changed7 schema fields changedv0.10.0
    • addedInput schema / properties / anio / description
      Added value: +"Fiscal year filter; defaults to the latest available year (the latest year may still be incomplete while filings arrive)."
    • addedInput schema / properties / ciiu_n1 / description
      Added value: +"Optional CIIU level-1 filter, e.g. \"C\", \"G\", \"I\"."
    • addedInput schema / properties / descending / description
      Added value: +"Set true for \"top N\" style queries (e.g. highest ingresos_ventas/roe first)."
    • 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."
    • addedInput schema / properties / order_by / description
      Added value: +"Column to sort by (e.g. \"posicion_general\", \"activos\", \"roe\")."
  3. Changed9 schema fields changedv0.8.14
    • removedInput schema / properties / anio / title
      Removed value: -"Anio"
    • removedInput schema / properties / ciiu_n1 / title
      Removed value: -"Ciiu N1"
    • removedInput schema / properties / descending / title
      Removed value: -"Descending"
    • 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 / order_by / title
      Removed value: -"Order By"
    • removedInput schema / title
      Removed value: -"search_rankingArguments"
    • removedOutput schema / title
      Removed value: -"search_rankingDictOutput"
  4. First observedv0.8.12

TDQS

B3.2/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 scope constraints (single fiscal year, five-year window, CIIU filtering), but says nothing about result size, pagination behavior, or ranking methodology.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the ranking scope front-loaded and no filler. It is slightly cryptic in places (e.g. the trailing 'top-N by a column' clause) but every sentence carries weight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter tool with no output schema, the description covers scope but not what the ranked result contains (columns, ordering semantics beyond a sort key, output row shape). Schema and annotations carry the rest, so it is adequate but not complete.

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 all seven parameters are already documented in the schema, and the baseline is 3. The description reinforces the meaning of ciiu_n1, anio and descending (top-N), but adds no syntax or format detail beyond what the schema provides.

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

Purpose4/5

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

States a specific verb and resource: 'Rank Supercías companies by financial indicators', with additional scope (one fiscal year, last five years, optional CIIU letter). This clearly separates it from sibling lookups like search_companias or get_financials, though it never names an alternative explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to pick ranking versus single-company financial retrieval (get_financials) or plain company search (search_companias). The only hint is 'descending=true for top-N by a column', which is parameter usage, not tool-selection guidance.

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