Skip to main content
Glama

cronitor

by io.usefulapi

Create monitor

cronitor_create_monitor
Destructive

Creates a monitor in Cronitor (additive). Cronitor API: POST /monitors. Sends only the fields you provide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesUnique monitor id/key.
nameNoHuman-readable monitor name.
noteNoFree-form note stored on the monitor.
tagsNoTags to group/filter monitors.
typeYesMonitor type: job | check | heartbeat | site.
notifyNoNotification list names to alert.
requestNoFor type=check: {url, method?, headers?, body?, ...}.
scheduleNoCron expression (job) or interval string, e.g. '0 9 * * *' or 'every 5 minutes'.
assertionsNoAssertions, e.g. "response.code = 200".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations provide destructiveHint=true; description adds 'additive' and 'Sends only the fields you provide', clarifying behavioral traits beyond annotations. No contradictions.

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?

Two sentences with no unnecessary words. Front-loaded purpose and key API detail. Every sentence adds value.

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?

No output schema, but description covers creation purpose, API method, and partial field behavior. Lacks return value info, but sufficient for a create tool with well-documented schema.

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 describes all 9 parameters with 100% coverage. Description adds only 'Sends only the fields you provide' which reinforces optionality. Baseline 3 is appropriate.

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?

Clearly states 'Creates a monitor in Cronitor (additive)'. Specifies the API endpoint (POST /monitors) and explicitly says 'additive', distinguishing from update/delete siblings.

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

Usage Guidelines3/5

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

Does not explicitly state when to use this tool versus alternatives like cronitor_update_monitor. Provides guidance via 'Sends only the fields you provide' but lacks direct when/when-not context.

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

All cronitor toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct action: create, delete, get, list, ping, update. There is no ambiguity or overlap between them.

Naming Consistency5/5

All tools follow the 'cronitor_<verb>_monitor' pattern with snake_case and consistent verb placement. Minor pluralization in 'list_monitors' is standard for listing endpoints.

Tool Count5/5

6 tools cover the core lifecycle of monitors without unnecessary extras. The count is well-scoped for a monitoring server.

Completeness5/5

The set provides full CRUD operations plus telemetry via ping. There are no obvious gaps for managing monitors.

Resources