Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver estadísticas de uso de un trámite

get_tramite_estadisticas
Read-only

Fetch monthly counts of people served and complaints for one gob.ec procedure by trámite ID, covering data since mid-2021.

Instructions

Monthly attentions (people served) and complaints for one gob.ec trámite since mid-2021, one trámite at a time. Take tramite_id from search_tramites; for requirements and cost use get_tramite_info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
tramite_idYesThe procedure ID (e.g. "11752")

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.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / tramite_id / description
      Added value: +"The procedure ID (e.g. \"11752\")"
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / tramite_id / title
      Removed value: -"Tramite Id"
    • removedInput schema / title
      Removed value: -"get_tramite_estadisticasArguments"
    • removedOutput schema / title
      Removed value: -"get_tramite_estadisticasDictOutput"
  4. First observedv0.8.12

TDQS

A4.7/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 safety is covered. The description adds genuinely useful behavioral context beyond them: the data returned (monthly attentions/complaints), the coverage start date (mid-2021), and the single-trámite scope. It stops short of noting rate limits or result-size behavior, so it is not a 5.

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 dense sentences, front-loaded with what the tool returns and its scope, followed by the routing guidance. No filler or restatement of the name/title.

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

Completeness5/5

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

No output schema exists, yet the description names the returned metrics and their granularity, and the schema's format enum covers the output shape. For a two-parameter read tool with annotations handling safety, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are documented, making 3 the floor. The description adds value beyond the schema by telling the agent where tramite_id comes from (search_tramites), which the schema's bare example '11752' does not convey.

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+resource (monthly attentions and complaints for one gob.ec trámite), including the temporal scope (since mid-2021) and the one-trámite-at-a-time constraint. It also names the sibling to use for other trámite data, so an agent can distinguish it without opening schemas.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite ('Take tramite_id from search_tramites') and routes the agent away from this tool for other needs ('for requirements and cost use get_tramite_info'). The when-to-use and the alternative are both stated, not inferred.

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