Skip to main content
Glama
art-qalam-fr

Kaggle MCP Server

by art-qalam-fr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dataset_download

Download Kaggle dataset files by owner and dataset slug, optionally targeting a specific file. Returns a direct download URL for the requested data.

Instructions

Download dataset files. Returns download URL.

    Args:
        owner: Dataset owner username.
        dataset_slug: Dataset slug name.
        file_name: Specific file. Empty for all.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYes
file_nameNo
dataset_slugYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

The description implies a read-only operation by stating it returns a download URL, but it does not explicitly confirm this or disclose any potential side effects. Since no annotations are provided, the description carries the burden, and it is minimally sufficient.

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?

The description is short and front-loaded with the main action. However, it includes a docstring-style parameter listing that could be streamlined or omitted if the schema already provides the same info.

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 an output schema exists and no annotations, the description covers the core functionality and parameters. However, it lacks details on rate limits, file size limits, or behavior when downloading multiple files.

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?

With schema description coverage at 0%, the description adds brief explanations for each parameter (e.g., 'owner: Dataset owner username.'). While this adds basic meaning, it does not provide constraints, formats, or examples beyond what the schema shows.

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 clearly states 'Download dataset files. Returns download URL.' which specifies the action and resource. However, it does not differentiate from the sibling tool 'dataset_download_file', which likely has a similar purpose but with a different scope.

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?

The description provides no guidance on when to use this tool versus alternatives like 'dataset_download_file'. It does not mention any prerequisites, context, or exclusions.

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