Skip to main content
Glama

Secop Describir Dataset

secop_describir_dataset
Read-onlyIdempotent

Retrieve real column names and metadata for a datos.gov.co dataset using a configured key or Socrata ID, so you can understand its structure before querying.

Instructions

Devuelve columnas y metadatos reales de un dataset de datos.gov.co (clave configurada o ID Socrata).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "secop_describir_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetNosecop2_contratos

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds the meaningful fact that the call reaches the external datos.gov.co source and how the dataset is addressed. It does not say what happens with an invalid key or ID, or whether results are cached.

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?

One short front-loaded sentence naming the output (columns and metadata), the source, and the accepted identifier forms. Nothing is wasted and nothing is buried.

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?

An output schema exists, so return values need no explanation, and with a single optional parameter the tool is simple. However, the description leaves open how an agent discovers valid keys and whether the call errors on unknown IDs, which matters for an open-world tool.

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 0% and the schema only declares an untyped default of 'secop2_contratos'. The description compensates partially by explaining that the value is either a configured key or a Socrata ID, which is genuinely new meaning. It does not give the Socrata ID format (e.g. abcd-1234) or explain when the default 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?

States a specific verb and resource: it returns the real columns and metadata of a datos.gov.co dataset. That is clearly distinct from the sibling search/lookup tools, although no sibling is named explicitly.

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?

Usage is implied rather than stated: an agent must infer this is the introspection step used before querying a dataset. There are no explicit when-to-use/when-not rules and no named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.