Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar registros exclusivos de BIINEC

search_biinec_extras
Read-only

Search a curated set of INEC BIINEC registries unavailable elsewhere, including environmental modules, as a fallback when live BIINEC data is missing.

Instructions

Small curated list of INEC BIINEC registries found nowhere else (e.g. environmental modules). A last resort; not a live BIINEC search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree text matched against the registry's name/description (accent-insensitive).
formatNotext summary (default) or json structured result.text

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 / query / description
      Added value: +"Free text matched against the registry's name/description (accent-insensitive)."
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_biinec_extrasArguments"
    • removedOutput schema / title
      Removed value: -"search_biinec_extrasDictOutput"
  4. First observedv0.8.12

TDQS

A4/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 a genuine behavioral trait beyond them: the result set is small, curated, and static rather than a live query, which tells the agent not to expect comprehensive or fresh coverage. Return format and pagination are not described, but that is a minor gap here.

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 compact sentences with no filler. The scope constraint (curated, unique-only) is front-loaded and the disambiguation ('not a live BIINEC search') follows immediately, making it easy to scan and act on.

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 2-parameter, no-required-args, read-only search tool with no output schema, the description covers scope, usage posture, and data nature adequately. It lacks any indication of result size limits or how matches are ranked/returned, which is a small remaining gap.

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%: both 'query' (accent-insensitive free text matched against name/description) and 'format' (text vs json) are fully documented in the schema. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 (search) and a precisely scoped resource: a small curated list of INEC BIINEC registries 'found nowhere else (e.g. environmental modules).' It contrasts itself against a live BIINEC search, though it does not name a specific sibling tool, so an agent gets the scope but must infer the exact alternative.

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?

'A last resort; not a live BIINEC search' gives clear when-to-use context (only after other sources fail) and an implicit exclusion (do not use for general BIINEC lookups). It stops short of naming the tool to use instead, so routing is implied rather than explicit.

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