Skip to main content
Glama

list_datasets

Lists datasets uploaded with upload_dataset that still exist so you can confirm available inputs before rerunning or resuming Kaggle jobs.

Instructions

Datasets uploaded with upload_dataset that still exist.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 one real behavioral rule: results are filtered to datasets created through upload_dataset and to those that have not been removed. It says nothing about ordering, completeness of the list, permissions, or whether the call is read-only, which leaves meaningful gaps for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no wasted words, but it is not a well-formed sentence and buries the action entirely, so it is under-specified rather than concise. The scoping clause is front-loaded, which is the one structural strength.

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 shape need not be explained, and with zero parameters the surface is small. However, the description never states the operation outright, nor whether the listing is exhaustive or ordered, leaving the agent to infer the core action from the name alone.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is empty and fully described by construction.

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 names the resource and pins down its scope precisely: only datasets created via upload_dataset that still exist, which implicitly excludes deleted ones. It never uses an explicit verb such as 'list', so it reads as a noun fragment, but an agent can still tell what comes back and can distinguish it from upload_dataset and delete_dataset.

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 statement, no mention of alternatives (e.g., why not list_jobs or job_output), and no note on when the list would be empty. Usage is only inferable from the tool name and the 'still exist' qualifier.

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