Skip to main content
Glama

Create a monitor

create_monitor
Idempotent

Creates a monitor in a free slot of the workspace's plan. Premium monitors (multi-step transactions and code repositories) have slots of their own, on Pro and Business only. When every slot is in use the call fails with monitor_limit_reached: the user can upgrade at https://upheron.com/pricing or delete a monitor. Needs a write token.

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL, or host[:port] for network checks.
kindNoWhat to check. `heartbeat` and `webhook` wait for your calls instead of probing. `repository` reads a GitHub or GitLab repository's dependency manifests daily and alerts on vulnerabilities in them, on every plan; put the repository URL in `url` (optionally …/tree/branch/folder) and, for a private repository (Pro plan), an access token in `check_options.token`. `websocket` (a ws:// or wss:// URL) and `grpc` (host[:port]) are created on Pro and Business (Free answers `422` with `plan_required`).http
nameYesShown in alerts and on status pages.
chartsNoCharts on public status pages: uptime bars (the last 90 days, or the whole history), the last 24 hours of response time, or both.both
methodNoThe HTTP method of the check's request.GET
tab_idNoThe monitor tab (GET /monitor-tabs) the monitor is sorted into in the dashboard; `null` takes it out of its tab.
keywordNoText the response body must contain.
dns_watchNoEvery plan, `http` and `api` monitors: look up the host's A, AAAA and CNAME records and its zone's NS, MX, SPF and DMARC hourly, and alert when one changes, with the old and new values.
locationsNoLocation codes from GET /locations. Defaults to the first location.
port_scanNoBusiness plans, network and website checks: scan the common TCP ports of the host's verified addresses weekly (POST /monitors/{id}/ports/verify), and alert when a port opens. See /docs/port-scans.
ip_versionNoNetwork and website checks: `auto` connects over IPv4, or IPv6 when the host has no IPv4 address; `ipv4` and `ipv6` use only that. `ipv6` needs locations with IPv6 (`ipv6` in GET /locations). An IP address as the host sets it.auto
slo_targetNoEvery plan: an availability objective in percent, such as 99.9, over slo_window_days; null for none. Downtime is the time in incidents, less maintenance. The monitor's contacts are alerted when its error budget burns fast, is 50%, 75% and 90% used, and when it runs out. See /docs/reports#error-budgets.
timeout_msNoMilliseconds a check waits for the reply before it counts as failed.
status_pageNoCreating only: give the monitor its own published status page while the plan allows more pages. Send `false` when you manage status pages yourself.
header_watchNoEvery plan, `http` and `api` monitors: grade the page's security headers, cookie flags and HTTPS redirect with each website scan (weekly on Free, daily on paid plans), and alert when one that was there is gone or weaker. See /docs/website-changes.
request_bodyNoThe body sent with the check's request, such as JSON for a POST.
check_optionsNoKind-specific options, such as `json_path`/`expected_value` for `api`, `steps` for transactions, `warn_days` for ssl. Ports go in `url` as host:port. See /docs/api#check-options.
content_watchNoBusiness plans, `http` and `api` monitors: look at the page hourly, keeping only a fingerprint of its text, title and external scripts, and alert when the text changes by `content_threshold` percent or more, the title changes, a script from a new host appears or defacement phrases show up. Accept a change with POST /monitors/{id}/changes/accept.
expiry_alertsNo`http` and `api` monitors: check the domain registration and (for HTTPS) the TLS certificate daily. Domain alerts come 30, 14, 7, 3 and 1 days before expiry; certificate alerts only once automatic renewal should have happened (a sixth of the certificate's lifetime, at most 14 days). Uses no extra monitor.
repository_urlNoPro and Business, `http` and `api` monitors with vulnerability alerts: the website's GitHub or GitLab repository (optionally …/tree/branch/folder), whose lockfiles and manifests are read hourly for exact versions. A failed read opens no incident. `null` unlinks it and removes what it listed.
idempotency_keyNoAny unique string. Repeating a call with the same key within 24 hours returns the first monitor instead of creating another. Use one per intended monitor.
request_headersNoSent with the check; stored encrypted and never returned.
slo_window_daysNoThe rolling window of the availability objective, in days.
interval_secondsNoSeconds between checks, no faster than the plan allows (300 on Free, 10 on Pro).
lookalike_alertsNoPro and Business, `http` and `api` monitors: look up a few hundred typo and homoglyph spellings of the registered domain daily, and alert when one starts resolving or gains MX records.
repository_tokenNoAccess token for a private `repository_url`: on GitHub a fine-grained token with read-only Contents, on GitLab `read_api`. Stored encrypted and never returned (`repository_token_set` tells whether one is saved). Leave it out to keep it; `null` removes it.
subdomain_alertsNoPro and Business, `http` and `api` monitors: list the domain's subdomains from certificate transparency logs (through crt.sh, which can be days or weeks behind), resolve each daily, and alert on a new one and on a CNAME to a service that reports no site there (a subdomain takeover risk).
alert_channel_idsNoNotification contacts to alert. Defaults to all of the workspace's contacts.
content_thresholdNoWith `content_watch`: the share of the page's text, in percent, that must change to alert. Smaller changes become the new baseline.
failure_thresholdNoFailed checks in a row before an incident opens. The default alerts on the first failed check.
recovery_thresholdNoSuccessful checks in a row before the incident resolves.
alert_delay_minutesNoPro and Business plans: minutes the first outage alert waits after the incident opens (on top of `failure_threshold`). Nobody is alerted about, or hears the recovery of, an outage that ends sooner.
dns_address_changesNoWhat A and AAAA answers alert on: `network` when they move to another network (autonomous system), so CDNs rotating addresses do not alert; `address` on any address change, for a site on fixed addresses; `none` never.network
expected_status_maxNoThe highest HTTP status that counts as up; at least `expected_status_min`.
expected_status_minNoThe lowest HTTP status that counts as up.
escalation_policy_idNoBusiness plans: alert this escalation policy (GET /escalation-policies) about outages instead of `alert_channel_ids`, which still receive expiry and vulnerability alerts. `null` alerts the contacts.
repeat_alert_minutesNoPro and Business plans: repeat the outage alert to the monitor's contacts this often until someone acknowledges the incident or it recovers, at most 48 times. `null` sends it once.
vulnerability_alertsNoEvery plan, `http` and `api` monitors: scan the website for the software it runs (weekly on Free, daily on paid plans) and alert on newly published vulnerabilities in it, checked daily and within 15 minutes of a new advisory (OSV.dev with the GitHub Advisory Database, NVD, new CVE records, WPVulnerability and WordPress core advisories for WordPress, CISA KEV, endoflife.date).
confirmation_thresholdNoLocations that must fail a check at the same time for it to count as failed. 1, the default, is any location; with 2 of 3 locations, one failing location alone is no outage and alerts nobody. More than the monitor's locations counts as all of them.
vulnerability_severityNoThe lowest severity that alerts. Actively exploited vulnerabilities and releases reaching end of support always alert.high
heartbeat_grace_secondsNoFor heartbeat and webhook monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / content_threshold
      Added value: +{
      +  "default": 25,
      +  "description": "With `content_watch`: the share of the page's text, in percent, that must change to alert. Smaller changes become the new baseline.",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / content_watch
      Added value: +{
      +  "default": false,
      +  "description": "Business plans, `http` and `api` monitors: look at the page hourly, keeping only a fingerprint of its text, title and external scripts, and alert when the text changes by `content_threshold` percent or more, the title changes, a script from a new host appears or defacement phrases show up. Accept a change with POST /monitors/{id}/changes/accept.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / dns_address_changes
      Added value: +{
      +  "default": "network",
      +  "description": "What A and AAAA answers alert on: `network` when they move to another network (autonomous system), so CDNs rotating addresses do not alert; `address` on any address change, for a site on fixed addresses; `none` never.",
      +  "enum": [
      +    "address",
      +    "network",
      +    "none"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / dns_watch
      Added value: +{
      +  "default": true,
      +  "description": "Every plan, `http` and `api` monitors: look up the host's A, AAAA and CNAME records and its zone's NS, MX, SPF and DMARC hourly, and alert when one changes, with the old and new values.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / header_watch
      Added value: +{
      +  "default": true,
      +  "description": "Every plan, `http` and `api` monitors: grade the page's security headers, cookie flags and HTTPS redirect with each website scan (weekly on Free, daily on paid plans), and alert when one that was there is gone or weaker. See /docs/website-changes.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / lookalike_alerts
      Added value: +{
      +  "default": false,
      +  "description": "Pro and Business, `http` and `api` monitors: look up a few hundred typo and homoglyph spellings of the registered domain daily, and alert when one starts resolving or gains MX records.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / slo_target
      Added value: +{
      +  "description": "Every plan: an availability objective in percent, such as 99.9, over slo_window_days; null for none. Downtime is the time in incidents, less maintenance. The monitor's contacts are alerted when its error budget burns fast, is 50%, 75% and 90% used, and when it runs out. See /docs/reports#error-budgets.",
      +  "exclusiveMaximum": 100,
      +  "minimum": 50,
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / slo_window_days
      Added value: +{
      +  "default": 30,
      +  "description": "The rolling window of the availability objective, in days.",
      +  "enum": [
      +    7,
      +    30,
      +    90
      +  ],
      +  "type": "integer"
      +}
    • addedInput schema / properties / subdomain_alerts
      Added value: +{
      +  "default": false,
      +  "description": "Pro and Business, `http` and `api` monitors: list the domain's subdomains from certificate transparency logs (through crt.sh, which can be days or weeks behind), resolve each daily, and alert on a new one and on a CNAME to a service that reports no site there (a subdomain takeover risk).",
      +  "type": "boolean"
      +}
  2. Changed6 schema fields changed
    • addedInput schema / properties / expected_status_max / description
      Added value: +"The highest HTTP status that counts as up; at least `expected_status_min`."
    • addedInput schema / properties / expected_status_min / description
      Added value: +"The lowest HTTP status that counts as up."
    • addedInput schema / properties / method / description
      Added value: +"The HTTP method of the check's request."
    • addedInput schema / properties / recovery_threshold / description
      Added value: +"Successful checks in a row before the incident resolves."
    • addedInput schema / properties / request_body / description
      Added value: +"The body sent with the check's request, such as JSON for a POST."
    • addedInput schema / properties / timeout_ms / description
      Added value: +"Milliseconds a check waits for the reply before it counts as failed."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior. The description adds important behavioral context: plan slot limits, premium-monitor restrictions, the exact monitor_limit_reached failure, the upgrade/delete remedy, and the write-token requirement. It does not describe idempotency semantics, but annotations and the idempotency_key schema field cover that.

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?

Four short sentences, front-loaded with the core purpose followed by plan limits, failure mode, and authentication. Every sentence contributes useful information and there is no wasted wording.

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?

For a high-complexity 41-parameter create tool, the rich schema carries parameter detail and annotations carry safety/idempotency information, while the description covers quota, plan restrictions, failure behavior, and auth. Minor omissions such as explicit idempotency behavior or the status-page side effect are documented in the schema and do not materially hinder correct invocation.

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 all 41 parameters are already well documented in the schema. The description adds plan-level context but no parameter-specific meaning beyond what the schema provides, so the baseline score of 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?

States a specific verb and resource ('Creates a monitor') and adds the slot constraint, which clearly separates it from read/update siblings such as get_monitor and update_monitor. The premium-slot sentence further specifies the resource class.

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?

It supplies useful context—write token required, free slot needed, plan restrictions—but never explicitly says when to choose create_monitor over update_monitor or how to handle existing monitors. Usage is implied by the verb rather than contrasted with alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources