Skip to main content
Glama

Get one job

cron_get_job
Read-onlyIdempotent

Retrieve details for a specific cron job by exact name, including schedule, command, last run, live resources, and retry or slot state. Use it to inspect one job before checking run history or logs.

Instructions

Show details for one job (schedule, command, last run, live resources, retry/slot state). Use it when you know the job's name; use cron_list_runs for its run history, or cron_tail_job_logs for its output.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact job name, as cron_list_jobs returns it. An unknown name returns an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.73
    • addedInput schema / properties / name / description
      Added value: +"Exact job name, as cron_list_jobs returns it. An unknown name returns an error."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the operation read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful behavioral context by listing what details are returned, including schedule, command, last run, live resources, and retry/slot state.

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 tight sentences and front-loads the core purpose before routing guidance. Every clause contributes either scope or sibling differentiation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-job read with complete annotations and complete parameter schema coverage, the description is sufficient. It explains the returned detail categories and redirects adjacent use cases to the appropriate sibling tools.

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 100%, so the single parameter is already documented as an exact job name with an error on unknown values. The description reinforces this with 'when you know the job's name,' but adds little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Show details for one job,' and immediately enumerates the detail categories. It clearly distinguishes this retrieval tool from run-history and log-tail siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states the selection condition: use this when you know the job's name. It also names alternatives for adjacent needs, pointing to cron_list_runs for run history and cron_tail_job_logs for output.

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