Skip to main content
Glama
ElectionData MCP

ElectionData MCP

describe_dataset

Read-only

Retrieve the columns, coverage, join keys, and download links for one ElectionData.MY dataset to understand its structure before querying or joining it.

Instructions

Columns, coverage, join keys and download links of one dataset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and an output schema exists, so the safety profile and return shape are covered elsewhere. The description adds some content-level context by naming the metadata categories returned, but says nothing about failure behavior for unknown names or about whether download links are static or expiring.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded clause with zero filler, which is efficient. However, the telegraphic fragment style omits the verb and actor, so brevity is achieved partly by dropping information rather than by tight writing.

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?

The tool is simple (one parameter) and has an output schema, so return values need no explanation here. What is missing is the prerequisite for a correct call — how a dataset name is discovered — which matters given the presence of search_datasets and find_dashboard siblings.

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

Parameters2/5

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

The single 'name' parameter has 0% schema description coverage, so the schema supplies no semantics. The phrase 'of one dataset' weakly implies the parameter identifies a dataset, but the description never says whether it must be an exact name, a slug, or an ID, nor where to obtain a valid value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('one dataset') and enumerates the metadata it surfaces (columns, coverage, join keys, download links), so the gist is recoverable. But it is a noun phrase with no verb, and it never distinguishes itself from siblings such as search_datasets or data_access, which an agent could easily confuse with it.

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 when-to-use statement at all. The description does not say to call this after finding a dataset via search_datasets, nor does it rule out any alternative, leaving the agent to guess the workflow.

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