Skip to main content
Glama

Job status

cron_get_status
Read-onlyIdempotent

Check every cron job's status—running, disabled, or scheduled—page by page for a quick overview of all jobs.

Instructions

Show each job's status: running, disabled, or scheduled, one page at a time. Use it for a quick check of every job; use cron_list_jobs for schedules, next runs, and last outcomes, or cron_get_job for one job's details.

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": "cron_get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost jobs to return (default and maximum 200).
offsetNoRows to skip. Pass the previous page's nextOffset to get the next page.

Output Schema

NameRequiredDescriptionDefault
pageYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.2.73
    • addedInput schema / properties / limit / default
      Added value: +200
    • addedInput schema / properties / limit / description
      Added value: +"Most jobs to return (default and maximum 200)."
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / offset / default
      Added value: +0
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip. Pass the previous page's nextOffset to get the next page."
    • addedInput schema / properties / offset / minimum
      Added value: +0
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the three status values returned and that results are paged ('one page at a time'), which is behavioral context not present in the annotations. It stops short of stating ordering or whether counts are included, but with an output schema present that is a minor gap.

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 sentences, zero waste: the first front-loads what is returned, the second routes to the correct sibling. Every clause earns its place.

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 two-param read-only paginated list with full schema coverage, an output schema, and rich annotations, the description supplies everything an agent needs to choose and invoke it. Only minor residual gaps (result ordering, whether the page carries a total count) are unaddressed.

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 100% with both limit and offset fully described, including the nextOffset paging hint, so the schema carries the load. The description's 'one page at a time' is consistent with that but adds no format or boundary detail beyond it. Baseline 3 applies.

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?

States a specific verb and resource ('Show each job's status') and enumerates the returned values (running, disabled, scheduled), so the agent knows exactly what data class this returns. It is clearly distinguishable from cron_list_jobs and cron_get_job, which are named in the same breath.

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?

Explicitly gives the selection rule: this tool for a quick status sweep of every job, cron_list_jobs for schedules/next runs/last outcomes, cron_get_job for a single job's details. Both alternatives and the condition that selects them are named, leaving nothing to inference.

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