Skip to main content
Glama
Sign In
kaggle-context

kaggle-context

by vks-g
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_discussions

List saved Kaggle competition discussion topics, solution write-ups first, with IDs for retrieving full discussion details.

Instructions

Saved discussion topics (solution write-ups first) with ids for get_discussion.

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_discussions"
  }
}

Input Schema

NameRequiredDescriptionDefault
competitionNo
solutions_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden. It discloses the default ordering (solution write-ups first), which is genuinely useful, but says nothing about read-only nature, pagination, filtering semantics, or result size.

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 compact sentence that is front-loaded with the resource and ordering. It is efficient and wastes little, though it borders on under-specification rather than true conciseness.

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 detailed. But for a two-parameter listing tool with zero schema coverage and no annotations, the description should explain the competition filter and solutions_only flag; it leaves both undefined.

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% and neither parameter (competition, solutions_only) is explained in the description. The phrase 'solution write-ups first' loosely touches the solutions concept but never names or defines the parameters, so the gap is largely unaddressed.

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

Purpose3/5

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

The description conveys that this retrieves saved discussion topics and notes a default ordering (solution write-ups first), so the resource is clear. However, the verb is only implied by the tool name, and it does not distinguish itself from the close sibling search_discussions or explain what 'saved' means versus a general search.

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?

It gives a partial next-step hint by noting the ids feed get_discussion, but offers no explicit when-to-use versus alternatives like search_discussions or get_discussion. An agent must infer the selection condition entirely.

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