Skip to main content
Glama
Sign In
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar siniestros de tránsito (ANT)

search_siniestros_ant
Read-only

Find Ecuador road-crash statistics from ANT and INEC records, including XLSX/CSV microdata and dataset links, filtered by year or keyword.

Instructions

Find Ecuador road-crash (siniestros de tránsito) data from ANT records: INEC quarterly/annual releases with XLSX/CSV microdata plus CKAN datasets (SPPAT deaths, ANT). ant.gob.ec is unreachable.

Input Schema

NameRequiredDescriptionDefault
anioNoYear filter on the title (0 = all years)
limitNoMax items per source (default 10, max 30)
queryNoOptional words that must appear in the title (e.g. "trimestre")
formatNotext summary (default) or json structured result.text
con_archivosNoAttach file links to this many newest INEC releases (default 2, max 5; 0 = none)

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. Addedv0.12.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive). The description adds useful context about source composition (INEC XLSX/CSV microdata, CKAN SPPAT deaths) and the unreachable ANT site, but omits details about result structure, pagination, or coverage limits.

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?

The description is compact and front-loaded, with the core purpose stated first and supporting source details following. Every sentence, including the note about ant.gob.ec being unreachable, earns its place.

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?

Given the multi-source search scope and absence of an output schema, the description is somewhat thin. It identifies the data and sources, and the schema covers the format parameter, but it does not describe what a result contains or how multiple sources are combined, leaving an agent partially informed.

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 is already documented in the schema. The description adds no parameter-level meaning beyond what the structured fields provide, making the baseline 3 appropriate.

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?

The description states a specific verb (Find) and resource (Ecuador road-crash data from ANT records) and names the underlying sources (INEC releases and CKAN datasets). It does not explicitly differentiate from siblings like search_inec_publicaciones or search_datasets, so it falls short of a 5.

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 explicit when-to-use guidance or named alternatives. The note that 'ant.gob.ec is unreachable' hints at why this tool exists but does not tell the agent when to choose it over the many other search tools available.

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