Skip to main content
Glama

kaggle_submissions

Retrieve recent Kaggle competition submissions and their scores to review model performance and compare leaderboard results.

Instructions

List your recent submissions and their scores 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_submissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
competitionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It correctly signals a read-only retrieval operation and adds the "recent" scoping hint, but leaves undefined how many entries "recent" means, whether pagination exists, and whether authentication is required.

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 sentence, front-loaded with the verb and resource, with no filler or redundant restatement of the tool name. Nothing could be trimmed without losing meaning.

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 not be explained, and the single parameter is structurally simple. However, the vague "recent" window and the absence of any alternative-tool routing leave the definition adequate but incomplete for an agent choosing among Kaggle tools.

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?

The single required parameter has 0% schema description coverage, so the description must compensate. The phrase "for a competition" does map the competition parameter to its purpose, but it adds no format guidance (slug vs. ID vs. display name) that the schema lacks.

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: "List your recent submissions and their scores," scoped to "a competition." An agent can tell this enumerates submissions rather than submitting them (kaggle_submit) or ranking entries (kaggle_leaderboard), though the description never names those siblings to differentiate explicitly.

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 guidance, no prerequisites, and no mention of alternatives such as kaggle_submit for creating a submission or kaggle_leaderboard for rankings. The agent must infer the retrieval-only context entirely from the verb "List."

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