Skip to main content
Glama

list_jobs

Lists all jobs submitted from this machine, newest first, and optionally refreshes each job's status from Kaggle.

Instructions

All jobs submitted from this machine, newest first. refresh=True asks Kaggle for status.

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

Input Schema

NameRequiredDescriptionDefault
refreshNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose non-obvious behavior: the result set is scoped to this machine, ordering is newest-first, and refresh=True performs a remote call to Kaggle (a latency/network hint, especially since it defaults to true). It stops short of saying what refresh=False does (presumably local cached data) or whether the call can be slow or rate-limited.

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?

Two short sentences, zero filler, with the scope constraint front-loaded followed by the one behavioral caveat. Nothing could be trimmed without losing information.

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 not be described, and the tool is low complexity with one optional boolean. The remaining gap is sibling routing (job_status vs list_jobs) and the semantics of refresh=False, which keeps it from being fully complete.

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 description coverage is 0%, so the description must compensate for the single parameter. It explains the refresh=True case as querying Kaggle for status, which adds real meaning beyond the bare boolean, but leaves the False case (local/cached results) and the cost of the default implicit.

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 ('All jobs') plus two differentiating properties: scope ('submitted from this machine') and ordering ('newest first'). It is clearly distinguishable from delete_dataset or submit_job, though it never explicitly contrasts itself with the closely related job_status or job_logs siblings.

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: the note about refresh=True suggests the caller uses this to get current status from Kaggle, but there is no explicit when-to-use, when-not-to-use, or pointer to job_status/job_logs for per-job detail. The agent must infer routing from tool names alone.

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