Skip to main content
Glama
Sign In

Croncool Cron Jobs

by cool.cron
OverviewDiscussionsAdmin

Check webhook delivery health

list_webhook_subscriptions
Read-onlyIdempotent

Use this when the user wants to read CronCool webhook subscription configuration and recorded delivery failures. Returns each subscription's endpoint origin, events, active state, consecutive failures, auto-disabled flag and last delivery time, 20 by default. Works only with a signed-in user session, not an API key. Not for changing or re-enabling a webhook.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many subscriptions to return, from 1 to 100; defaults to 20
projectIdNoOnly subscriptions of this project

Output Schema

NameRequiredDescriptionDefault
subscriptionsYesEndpoint origins and delivery health; autoDisabled marks a subscription switched off after 20 consecutive failures. Full endpoint paths and queries, signing secrets, payloads and ownership fields are excluded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of subscriptions to return (default 20, max 100)"New value: +"How many subscriptions to return, from 1 to 100; defaults to 20"
    • changedInput schema / properties / projectId / description
      Previous value: -"Only return subscriptions of this project"New value: +"Only subscriptions of this project"
    • addedOutput schema / properties / subscriptions / description
      Added value: +"Endpoint origins and delivery health; autoDisabled marks a subscription switched off after 20 consecutive failures. Full endpoint paths and queries, signing secrets, payloads and ownership fields are excluded."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: the signed-in session requirement (explicitly not an API key) and the default page size of 20. It stops short of ordering/pagination or failure-recording semantics, so it is strong but not exhaustive.

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?

Four tight sentences, front-loaded with the trigger and the return payload, then auth constraint, then exclusion. The trailing ', 20 by default' is awkwardly spliced onto the field list and duplicates schema information, a minor structural blemish.

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 an output schema present, enumerated return fields are bonus rather than necessity, and annotations cover the safety profile. The auth prerequisite and the read-only boundary are disclosed, leaving only minor gaps such as how results behave when projectId is omitted.

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%, so both `limit` and `projectId` are fully documented in the schema and the baseline is 3. The description repeats the default of 20 and never mentions the projectId scoping parameter, so it adds nothing the schema does not already carry.

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?

Opens with a specific trigger and verb+resource: reading CronCool webhook subscription configuration and recorded delivery failures. No sibling tool covers webhooks, so the scope is unambiguous, and the closing 'Not for changing or re-enabling a webhook' pins down the boundary further.

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?

Gives an explicit trigger ('Use this when the user wants to read...') and an explicit exclusion ('Not for changing or re-enabling a webhook'), which is exactly the when/when-not split an agent needs. No webhook-mutation sibling exists to name, so no routing is left ambiguous.

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 toolsInspect
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