Skip to main content
Glama

kaggle_submit

Submit a local or remote runtime file, such as a run's submission.csv, to a Kaggle competition. Use it to deliver predictions and record a submission message.

Instructions

Submit a file to a competition.

file: a path on this computer, or a path on the connected runtime (for example a run's submission.csv), which is fetched first.

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>",
      "file": "<file>"
    },
    "name": "kaggle_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
messageNovia gpu-bridge
competitionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does add genuinely useful context that the file may live locally or on the connected runtime and is fetched first, which no other field conveys. However, it omits that submissions are a scarce, rate-limited resource with per-day quotas and that submission results are asynchronous to scoring — material facts for a mutation tool.

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?

Two short sentences, front-loaded with the action, and the file-path clarification is placed where it is needed. Nothing is padded, though the brevity leaves the remaining parameters unaddressed rather than the text being wasteful.

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, but for a destructive/irreversible mutation against a quota-limited endpoint with 0% schema coverage, the definition says too little. Missing are competition identifier format, the meaning of 'message', and any consequence of a successful or failed submission.

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?

Schema description coverage is 0%, so the description must compensate and mostly does not. It clarifies only the 'file' parameter (local path or path on the connected runtime, fetched before submit); the required 'competition' parameter is never explained (presumably a slug or ID) and the optional 'message' parameter with default 'via gpu-bridge' is unmentioned entirely.

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 ('Submit a file to a competition'), which is immediately distinguishable from listing-oriented siblings like kaggle_competition_files or kaggle_submissions. It does not explicitly name a sibling or state what it is not, so a 4 rather than 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 Guidelines3/5

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

Usage is implied by the verb: this is the tool you use to enter a competition. There is no explicit when-not guidance, no mention of prerequisites such as having a competition entry accepted or a rules agreement, and no routing to alternatives like a plain file upload tool.

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