Skip to main content
Glama
Sign In
mcp-kaggle-tool

mcp-kaggle-tool

by MikeyBeez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kaggle_get_notebook_status

Retrieve the current execution status of a Kaggle notebook. Provide the kernel slug (username/notebook-slug) to check if it's running, completed, or failed.

Instructions

Get the status of a notebook execution

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": {
      "kernelSlug": "<kernelSlug>"
    },
    "name": "kaggle_get_notebook_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
kernelSlugYesNotebook identifier (username/notebook-slug)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It fails to specify what 'status' means (e.g., possible values like pending, running, completed, failed), idempotency, or authentication requirements. This leaves uncertainty for the agent.

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 a single sentence with no redundancy, achieving maximum efficiency. However, it is too short to provide necessary context, which reduces its overall effectiveness. Still, it is well-structured for its length.

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?

Given no output schema and no annotations, the description should provide more context about return values, possible statuses, and usage hints. It is insufficiently complete for an agent to reliably use the tool.

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?

Schema coverage is 100% for the single parameter, and the description adds no additional semantic information beyond the schema's 'Notebook identifier (username/notebook-slug)'. Baseline is 3, and the description does not improve it.

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

Purpose5/5

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

The description 'Get the status of a notebook execution' clearly states the action (get status) and resource (notebook execution). It distinguishes from siblings like kaggle_run_notebook (triggers execution) and kaggle_download_notebook_output (downloads results).

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?

The description lacks any guidance on when to use this tool. It does not mention typical use cases (e.g., after running a notebook) or alternatives like polling. The intended usage is implied but not explicit.

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