Skip to main content
Glama
Sign In
kaggle-context

kaggle-context

by vks-g
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_discussion

Fetch a Kaggle forum topic with its opening post and top comments. Live retrieval occurs if not cached, helping you inspect competition discussions.

Instructions

One topic with its opening post and top comments. Fetches live if not saved.

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": {
      "topic_id": "<topic_id>"
    },
    "name": "get_discussion"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNo
topic_idYes
competitionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does state that the tool 'fetches live if not saved,' which is useful caching context. However, it omits permissions, error handling, rate limits, and other operational traits expected for a fully unannotated tool.

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?

The description is two short sentences with no wasted words, and it front-loads the resource content before the fetching behavior. It is appropriately sized for the amount of information it chooses to convey.

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 explained, but the input schema has three parameters with zero description coverage and no annotations. The description does not clarify the optional 'part' or 'competition' parameters, leaving the definition incomplete for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%, with three parameters (topic_id, part, competition) that are never mentioned or explained in the description. The description provides no meaning beyond the bare schema names, so it fails to compensate for the documentation gap.

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?

The description identifies a specific resource and its returned content: 'One topic with its opening post and top comments.' It implies retrieval through 'Fetches live if not saved,' but does not explicitly distinguish this from siblings like list_discussions or search_discussions.

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?

The description gives no guidance on when to use this tool versus alternatives such as list_discussions or search_discussions. It only implies a single-topic use case through its wording.

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