Skip to main content
Glama

kaggle_competition_files

Lists downloadable files for a Kaggle competition so you can identify datasets and assets available before running training or submissions.

Instructions

List the downloadable files for a competition.

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": {
      "competition": "<competition>"
    },
    "name": "kaggle_competition_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
competitionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full behavioral burden and falls short. It does not disclose whether Kaggle credentials are required, whether accepting competition rules is a precondition, or whether the listing is paginated or truncated. The phrase 'downloadable' hints that some files may be excluded, but that filtering rule is never explained.

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 front-loaded sentence with no filler or redundancy. It is efficiently structured, though the terseness contributes to the gaps in the other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 not be described. However, for a credentialed third-party API call with no annotations and an undocumented identifier parameter, the definition omits the essential call-time context (auth, identifier format, rule-acceptance gating).

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 required parameter 'competition' has 0% schema description coverage, so the description must define it and does not. It never says whether the value is a slug, a numeric ID, or a URL, nor whether it must match an already-joined competition — a real risk for a one-parameter tool where the call fails outright if the format is wrong.

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 names a specific verb ("List") and a specific resource ("downloadable files for a competition"), so an agent knows exactly what it returns. It does not explicitly differentiate itself from siblings like kaggle_leaderboard or kaggle_submissions, but the resource noun is distinct enough to avoid confusion.

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 explicit guidance on when to call this tool versus alternatives such as download_file or kaggle_submissions. Usage is only loosely implied by 'downloadable files' — an agent could guess this is a discovery step before downloading, but nothing in the text states a condition or prerequisite.

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