hookpulse

Create endpoint

create_endpoint

Create a monitor for a routine. Use cron, tz and grace_sec for a schedule, or interval_sec for a fixed check-in interval. Set max_duration_sec to detect an open run that exceeds its time limit. Without an owner token, creation returns guest_token; keep it private for later calls. Read billing before a paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.

Input Schema

Name	Required	Description
`tz`	No	IANA time zone for cron, default UTC
`cron`	No	five-field cron, e.g. 0 3 * * *
`name`	Yes	how you will recognise the routine in an alert; required, trimmed, max 80 chars, punctuation alone is rejected
`tags`	No	up to 8 tags to group the monitor; lower-cased, [a-z0-9._-], max 32 chars each
`alert_to`	No	Authorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel.
`alert_url`	No	Public HTTPS URL that receives a POST on a miss (Slack Incoming, Discord, n8n).
`grace_sec`	No	tolerance after the scheduled time, default 90, min 30
`guest_token`	No	Existing owner token, if available.
`interval_sec`	No	Tolerated silence, in seconds. Below the free minimum, it costs.
`paused_until`	No	maintenance window end (UTC ISO), max 30 days ahead
`alert_repeat_sec`	No	gap before the same incident alerts again, 3600..2592000; null keeps the 86400 default
`max_duration_sec`	No	ceiling for an open run in seconds, 60..86400; null or 0 turns it off

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026

changedInput schema / properties / alert_to / description

Previous value: -"E-mail to alert on a miss; without it, the account is alerted."New value: +"Authorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel."

addedInput schema / properties / guest_token / description
```
Added value: +"Existing owner token, if available."
```

changedInput schema / required

Previous value: -[
-  "guest_token",
-  "name"
-]New value: +[
+  "name"
+]

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / interval_sec / description

Previous value: -"Tolerated silence, in seconds."New value: +"Tolerated silence, in seconds. Below the free minimum, it costs."

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / interval_sec / description

Previous value: -"Tolerated silence, in seconds. Below the free minimum, it costs."New value: +"Tolerated silence, in seconds."

Changed1 schema field changedSep 8, 2026

changedInput schema / properties / name / description

Previous value: -"Name to recognise the monitor in the alert."New value: +"how you will recognise the routine in an alert; required, trimmed, max 80 chars, punctuation alone is rejected"

Changed7 schema fields changedSep 8, 2026

addedInput schema / properties / alert_repeat_sec

Added value: +{
+  "description": "gap before the same incident alerts again, 3600..2592000; null keeps the 86400 default",
+  "type": "number"
+}

addedInput schema / properties / cron

Added value: +{
+  "description": "five-field cron, e.g. 0 3 * * *",
+  "type": "string"
+}

addedInput schema / properties / grace_sec

Added value: +{
+  "description": "tolerance after the scheduled time, default 90, min 30",
+  "type": "number"
+}

addedInput schema / properties / max_duration_sec

Added value: +{
+  "description": "ceiling for an open run in seconds, 60..86400; null or 0 turns it off",
+  "type": "number"
+}

addedInput schema / properties / paused_until

Added value: +{
+  "description": "maintenance window end (UTC ISO), max 30 days ahead",
+  "type": "string"
+}

addedInput schema / properties / tags

Added value: +{
+  "description": "up to 8 tags to group the monitor; lower-cased, [a-z0-9._-], max 32 chars each",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / tz

Added value: +{
+  "description": "IANA time zone for cron, default UTC",
+  "type": "string"
+}

Changed4 schema fields changedSep 6, 2026

addedInput schema / properties / alert_to / description

Added value: +"E-mail to alert on a miss; without it, the account is alerted."

addedInput schema / properties / alert_url / description

Added value: +"Public HTTPS URL that receives a POST on a miss (Slack Incoming, Discord, n8n)."

addedInput schema / properties / interval_sec / description

Added value: +"Tolerated silence, in seconds. Below the free minimum, it costs."

addedInput schema / properties / name / description

Added value: +"Name to recognise the monitor in the alert."

First observedSep 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish that this is a non-idempotent, non-destructive write, and the description adds real behavioral context beyond them: the guest_token returned without an owner token and the need to keep it private, the HTTP 402 on charged requests, and that alert timing depends on the check cycle. Several sentences ('Your agent can stop after setting up the monitor', 'A check-in proves the signal arrived, not that a backup can be restored') are vague enough that their operational meaning is unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded and the key operational facts (mode selection, guest_token, 402) come early. However, the paragraph runs to nine sentences and several trailing lines read as defensive hedging rather than actionable guidance, diluting the signal.

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?

For a 12-parameter mutation tool with no output schema, the description covers auth, billing and alerting well, but omits what the response actually contains and how the created monitor is signalled afterward (the ping slug/URL used by signal_slug, ping_slug, ping_ingest). That is a meaningful gap for an agent trying to complete setup end to end.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds combinatorial meaning the schema cannot express: which parameters form the cron-schedule mode versus the interval mode, and that max_duration_sec detects an open run exceeding its limit. It does not explain interaction rules for paused_until or alert_repeat_sec, but the mode-selection guidance lifts it above baseline.

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 opening sentence names a specific verb and resource ('Create a monitor for a routine') and the rest clarifies the two monitoring modes. It is clear what the tool does, though it never explicitly distinguishes itself from siblings like create_site or import_crontab, which also create monitoring resources.

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?

It gives concrete selection guidance between modes ('cron, tz and grace_sec for a schedule, or interval_sec for a fixed check-in interval') and directs the agent to read billing before choosing a paid option. It stops short of saying when to use this tool instead of create_site or import_crontab.

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

All hookpulse 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.

Create endpoint

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources