Skip to main content
Glama

thanaton_manage_crons

List, register, or delete scheduled cron jobs for serverless background invocations. Specify cron expressions and HTTP routes to manage recurring tasks.

Instructions

List, register, or delete scheduled cron jobs for serverless background invocations.

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": {
      "project_id": "<project_id>",
      "action": "<action>"
    },
    "name": "thanaton_manage_crons"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoHTTP route path to invoke (for add, e.g., /api/cron/cleanup)
actionYesAction to perform
cron_idNoCron job ID (required for delete)
scheduleNoCron expression (for add, e.g., '0 * * * *')
project_idYesTarget project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

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 behavioral burden, yet it says nothing about deletion being irreversible, whether removing a cron stops in-flight invocations, what permissions are required, or what a successful response looks like. For a tool whose 'delete' action is destructive, this is a meaningful disclosure 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?

A single sentence with the action set and resource front-loaded and zero filler. It is appropriately sized for the amount of information it chooses to convey.

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

Completeness3/5

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

The input schema is complete and fully described, which covers most of what an agent needs to construct a call. However, with no annotations and no output schema, the description should compensate for the missing safety and response context on the destructive delete path, and it does not.

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%, with per-parameter descriptions covering path, schedule, cron_id, project_id and the action enum, so the baseline is 3. The description adds only the loose mapping of 'register' to the 'add' action and nothing about expression syntax, timezone, or mutual exclusivity of parameters across actions.

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?

The description gives three specific verbs (list, register, delete) against a named resource (scheduled cron jobs) with the domain purpose (serverless background invocations). It is clear what the tool does, though it does not explicitly distinguish itself from adjacent tools like thanaton_manage_deploy_hooks or thanaton_manage_routes, which an agent might confuse with scheduled work.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool versus related lifecycle tools, nor any explanation of the per-action prerequisites (for example that 'add' needs both a schedule and a path, or that 'delete' should be used rather than disabling). The agent must infer usage entirely from the action enum.

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

Deploy Server

Other Tools