Skip to main content
Glama

cron_list

Read-onlyIdempotent

List cron triggers for a project (or all your projects). Each row includes timezone, last_run_at, last_run_status, last_run_job_id, bounded last_error_code/last_error diagnostics, and next_run_at. A task that has never run returns null for every last-run field. job_get with last_run_job_id returns full bounded attempt history. Passing project_id also returns policy — the project owner's plan name, the smallest interval a new or edited schedule may have, and how many scheduled tasks the project may hold.

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

Input Schema

NameRequiredDescriptionDefault
project_idNoOptional — filter to one project. Accepts UUID, subdomain, or 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and idempotentHint, and the description adds meaningful behavior: per-row diagnostics, null values for never-run tasks, bounded error fields, next_run_at, and conditional policy data. It omits pagination, ordering, and permission details, which keeps it from a 5.

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?

The description is front-loaded and every sentence adds concrete value, especially given there is no output schema. The field enumeration is dense but justified; it does not waste words on repetition.

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?

With no output schema, the description does substantial work explaining return fields, null semantics, diagnostics, and the job_get handoff. It is not fully complete because it does not cover pagination, result ordering, or access requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so project_id syntax is already documented. The description adds useful conditional semantics: passing project_id also returns the project policy, including plan name and scheduling limits.

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 opens with a specific verb and resource: 'List cron triggers for a project (or all your projects).' It clearly distinguishes this read/list operation from sibling mutation tools such as cron_create, cron_update, and cron_delete.

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

Usage Guidelines4/5

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

It states the scope clearly: list cron triggers for one project or all projects, and it points to job_get for deeper attempt history. It does not explicitly say when not to use it or compare it against other list-style siblings, but the context is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources