Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver metadata de una encuesta ANDA

get_anda_survey_info
Read-only

Retrieve full metadata for an ANDA survey using its idno, including scope, variables, microdata availability, and access terms.

Instructions

Full metadata for one ANDA survey (string idno from search_anda): scope, variables, microdata availability and access terms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idnoYesSurvey idno or numeric id from search_anda ("idno" or "id" field)
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. Changed1 schema field changedv0.12.0
    • changedInput schema / properties / idno / description
      Previous value: -"Survey identifier from search_anda (the \"idno\" field)"New value: +"Survey idno or numeric id from search_anda (\"idno\" or \"id\" field)"
  3. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / idno / description
      Added value: +"Survey identifier from search_anda (the \"idno\" field)"
  4. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / idno / title
      Removed value: -"Idno"
    • removedInput schema / title
      Removed value: -"get_anda_survey_infoArguments"
    • removedOutput schema / title
      Removed value: -"get_anda_survey_infoDictOutput"
  5. First observedv0.8.12

TDQS

A3.6/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 the content shape of the metadata (variables, microdata availability, access terms), which is useful, but discloses nothing extra about auth needs, rate limits, or edge cases.

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?

A single efficient sentence with the resource identifier front-loaded and the returned facets listed after. Nothing is wasted, though the parenthetical is slightly compressed.

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 carries the burden of telling the agent what comes back, and it does so by enumerating scope, variables, microdata availability and access terms. Annotations cover safety, so the remaining omission — return format details for text vs json — is minor.

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 both parameters are already documented in the schema, including the enum for 'format'. The description only restates that idno comes from search_anda and adds no syntax or format guidance beyond the schema — the baseline 3 for full coverage is 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?

Names a specific verb+resource ('Full metadata for one ANDA survey') and enumerates the returned facets (scope, variables, microdata availability, access terms). The search-then-detail relationship to search_anda is implied rather than stated as an explicit contrast, so it falls just 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 Guidelines4/5

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

The parenthetical 'string idno from search_anda' establishes the prerequisite workflow: the agent must first call search_anda to obtain an idno. It gives clear context for when this tool applies but offers no explicit when-not guidance or alternative siblings.

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