Skip to main content
Glama

list_jobs

Retrieve a user's cron jobs, optionally filtered by machine ID, so you can review scheduled tasks per machine.

Instructions

List the user's cron jobs, optionally filtered by machine.

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
machine_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and falls short: it doesn't say whether results are paginated, how they are ordered, what fields a job includes, or what happens if the machine filter matches nothing. The only behavioral detail added is the user-scoping and optional filtering, which is thin 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.

Conciseness4/5

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

A single efficient sentence with the resource front-loaded and the optional modifier trailing correctly. Nothing is wasted, though the brevity leaves useful detail unstated rather than the sentence being poorly structured.

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?

No output schema and no annotations mean the description must explain both the return shape and the safety profile, and it does neither. For a simple read-only list tool the gaps are survivable but still significant: return contents, pagination, and filter semantics are all undocumented.

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?

With one parameter at 0% schema description coverage, the description must supply the meaning, and it does identify machine_id as an optional machine filter. It does not clarify whether the value is an ID or a name, or how matching behaves, so the compensation is partial.

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 ('List the user's cron jobs') with a clear ownership scope. It doesn't distinguish itself from siblings like list_runs or sync_jobs, so an agent must infer which listing tool fits from names alone.

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?

'Optionally filtered by machine' implies the primary use case (browse all jobs, or narrow to one machine) but gives no explicit when-to-use versus when-not guidance, no mention of alternatives such as sync_jobs, and no prerequisites.

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