Skip to main content
Glama
Sign In
kaggle-context

kaggle-context

by vks-g
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_competitions

List competitions already fetched on this machine, with the default marked, to see what cached data is available.

Instructions

List competitions already fetched on this machine (the default is marked).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_competitions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 burden, and it does disclose two useful traits: results are local/cached rather than remote, and the default entry is flagged. It says nothing about ordering, whether fetching is triggered, rate limits, or auth, though for a zero-argument local listing the residual risk is low.

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 front-loaded sentence with the scope constraint and the default-marker detail packed in; nothing is padded and nothing is redundant with the schema.

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

Completeness4/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 no explanation, and a zero-parameter read-only listing is a simple contract. The description covers scope and the default marker; the only gap is the missing routing hint toward fetch_competition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The parenthetical noting that the default is marked adds a small amount of interpretive value about the output, but there are no parameters whose semantics need explaining.

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 (List) and resource (competitions) plus a meaningful scope qualifier: entries are local/cached ('already fetched on this machine'). That scope implicitly separates it from fetch_competition, but no sibling is named outright, so differentiation is left partly to inference.

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 only implied: by saying competitions are 'already fetched on this machine,' the agent can infer it must call fetch_competition first and that this tool is a local inventory view. There is no explicit when-to-use instruction, no exclusions, and no named alternative.

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