Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver historial financiero de una compañía

get_financials
Read-only

Retrieve a company's Supercías financial history for the last five fiscal years by expediente or RUC, including revenue, assets, equity, profit, employees, and ratios; optionally filter by year.

Instructions

One company's Supercías financial history (last five fiscal years): revenue, assets, equity, profit, employees and ratios. Takes expediente or RUC.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoOptional single fiscal year filter.
formatNotext summary (default) or json structured result.text
expediente_or_rucYesThe company's Supercías "expediente" number (from search_companias/get_compania_info) or its 13-digit RUC.

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. Changed3 schema fields changedv0.10.0
    • addedInput schema / properties / anio / description
      Added value: +"Optional single fiscal year filter."
    • addedInput schema / properties / expediente_or_ruc / description
      Added value: +"The company's Supercías \"expediente\" number (from search_companias/get_compania_info) or its 13-digit RUC."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
  3. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / anio / title
      Removed value: -"Anio"
    • removedInput schema / properties / expediente_or_ruc / title
      Removed value: -"Expediente Or Ruc"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / title
      Removed value: -"get_financialsArguments"
    • removedOutput schema / title
      Removed value: -"get_financialsDictOutput"
  4. First observedv0.8.12

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description usefully adds the 'last five fiscal years' temporal bound and the returned field set, but says nothing about rate limits, data freshness, or behavior when a year filter yields no data.

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 efficient sentences with no filler, and the resource/scope is front-loaded ahead of the input note. It is terse to the point of omitting the optional anio/format parameters, but nothing is wasted.

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 no output schema, the description compensates by naming the returned fields and the five-year window, and annotations cover safety. It is largely complete for a single-company read tool, though it could note the year-filter and format behavior.

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%, so all three parameters are already documented in the schema (including the anio filter and text/json format). The description only restates the identifier input, adding no syntax or format detail 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?

The description states a specific resource (one company's Supercías financial history), scope (last five fiscal years), and enumerates the returned fields (revenue, assets, equity, profit, employees, ratios). An agent can tell this is the financial-history tool rather than the general company-info tool (get_compania_info) from the description alone.

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?

It states the accepted identifiers ('Takes expediente or RUC'), which hints at usage, but never says when to prefer this over get_compania_info or search_companias, and gives no exclusions or prerequisites. 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