Lists all cron jobs on the account, showing command, schedule, and status. Enables easy auditing of automated tasks.
List all cron jobs on the account
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_cron_jobs"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but it only states the action without revealing any behaviors such as return format, ordering, permissions, or potential side effects. It adds no transparency beyond what the tool's name implies.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, compact sentence that gets straight to the point with no wasted words or redundant phrasing. It is optimally concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, simple list tool, this description is sufficiently complete to understand its purpose and scope. It lacks only minor details like the exact structure of the output, but no output schema exists and the return value is reasonably inferable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so a baseline score of 4 is appropriate. The description does not need to explain parameters since there are none, and the schema has no properties to clarify.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'List' with a clear resource 'all cron jobs' and scope 'on the account'. It clearly distinguishes from sibling tools like create_cron_job, edit_cron_job, and delete_cron_job by indicating a read-only enumeration action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The usage is implied by the action verb 'List' and the resource 'cron jobs', making it obvious when to use this tool relative to creating, editing, or deleting cron jobs. However, there is no explicit statement of when to use it or comparison with alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.