Croncool Cron Jobs

Get cron job details

get_job

Read-onlyIdempotent

Use this when the user wants to read the scheduling configuration and latest execution metadata of one CronCool job selected by its exact identifier. Returns the job's name, cron expression, type, target origin, HTTP method, content type, enabled state and last run status and time, or not-found. Not for running the job.

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

Input Schema

Name	Required	Description	Default
`jobId`	Yes	Job id (uuid)

Output Schema

Name	Required	Description	Default
`job`	Yes	Null when not found, including another organization's job. Request payloads and credential-bearing URL paths, queries, fragments and userinfo are never returned.
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

addedOutput schema / properties / job / description

Added value: +"Null when not found, including another organization's job. Request payloads and credential-bearing URL paths, queries, fragments and userinfo are never returned."

First observedSep 17, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered externally. The description adds the not-found outcome and notes that only the latest run is returned, which is modest added value beyond the annotations but not deep behavioral detail.

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?

Two sentences, front-loaded with the usage trigger and purpose, with the exclusion appended last. The return-field enumeration is slightly list-heavy but still compact and nothing is wasted.

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?

An output schema exists, so the description need not explain return values, yet it still names the key returned fields and the not-found case. Combined with fully covered annotations and a documented parameter, the definition is sufficient to invoke correctly.

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% and the single jobId parameter is documented as a uuid with length bounds. The description only restates this as 'exact identifier', adding little beyond what the schema already provides, so the 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 (read) and resource (scheduling configuration and latest execution metadata of one job), scoped to an exact identifier. It also distinguishes itself from siblings by ruling out execution ('Not for running the job'), so an agent can separate it from run_job and get_job_runs.

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?

Gives a clear trigger ('Use this when the user wants to read...') and an explicit exclusion for job execution. It does not, however, name get_job_runs as the alternative when the user wants execution history rather than latest status, leaving that inference to the agent.

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

All Croncool Cron Jobs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?