Skip to main content
Glama

kaggle_search_datasets

Search Kaggle datasets by keyword and return dataset references usable with cv_load_dataset, so you can locate data for computer vision training or experiments.

Instructions

Search Kaggle datasets by keyword (returns refs usable with cv_load_dataset).

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": {
      "query": "<query>"
    },
    "name": "kaggle_search_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden, and it does add real value by naming the return shape (dataset refs consumable by cv_load_dataset). It says nothing about Kaggle credential requirements, result limits, or whether the search hits the live API, which are meaningful gaps for an 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?

A single sentence with the action front-loaded and the return-value note attached as a compact parenthetical. Nothing is wasted and nothing needs to be skimmed past.

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?

For a one-parameter search tool with an output schema, the description covers purpose and how the result plugs into the next step. The remaining omissions (auth requirements, result count, empty-result behavior) are modest given the tool's simplicity and the presence of an output schema.

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 0% for the single query parameter, so the description must compensate. "By keyword" does clarify the matching semantics slightly (keyword rather than ref/URL), but gives no guidance on syntax, multi-term behavior, or formatting of the query string.

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 and resource ("Search Kaggle datasets") and adds the downstream consumer ("refs usable with cv_load_dataset"), which tells an agent what it gets back. It does not distinguish itself from the similar sibling hf_search, so it falls short of full sibling differentiation.

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 parenthetical implies the intended workflow: search first, then feed refs to cv_load_dataset. However, there is no explicit when-to-use versus hf_search, and no note on when keyword search is or isn't appropriate (e.g., browsing vs. exact ref lookup).

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