Skip to main content
Glama

Update Monitor Tool

update-monitor

Update a monitor by ID. Supports HTTP, keyword, TCP, ping, and DNS monitors. Requires Full Access MCP token and eligible paid plan.

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": {
      "monitor_id": "<monitor_id>"
    },
    "name": "update-monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL to monitor for http and keyword monitors
hostNoHostname or IP for tcp, ping, and dns monitors
nameNoMonitor display name
portNoTCP port number 1-65535 for tcp monitors
typeNoType of check: http, keyword, tcp, ping, dns, or heartbeat (Pro+, passive inbound check-in)
keywordNoKeyword to search for keyword monitors
timeoutNoResponse timeout in seconds: 5, 10, or 15
monitor_idYesThe UUID of the monitor to update
monitor_sslNoEnable SSL certificate monitoring for http/keyword monitors
keyword_typeNoAlert when keyword exists or does not exist
notify_uptimeNoEnable uptime/recovery notifications
check_intervalNoFrequency of checks in seconds
monitor_domainNoEnable domain expiry monitoring for http/keyword monitors
alert_thresholdNoConsecutive failures before alerting: 1, 2, 3, or 5
dns_record_typeNoDNS record type for dns monitors
monitor_consentNoEnable or disable the weekly Consent Scan, which records the cookies the page sets before and after consent (http/keyword only, counts toward the plan's Consent Scan limit). Reports observations, never a compliance verdict.
request_headersNoOptional HTTP request headers as objects with name and value
dns_expected_valueNoExpected DNS value for hijacking detection
monitor_page_speedNoEnable Page Speed monitoring when allowed by plan
pinned_region_codeNoLocation this monitor is checked from. Use list-check-regions for valid values; omit or send an empty string for automatic selection.
private_location_idNoUUID of one of your own Private Locations to check this monitor from instead of the Baromio fleet. Use list-private-locations for valid values. Only http, keyword, and tcp types are eligible.
accepted_status_codesNoHTTP monitors only: status codes 400-599 (at most 10) to count as up in addition to 200-399, for a URL that answers 401, 404 or 503 on purpose. Send an empty array to clear the list. Not available for keyword monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / timeout / description
      Previous value: -"Timeout in seconds: 15, 30, or 60"New value: +"Response timeout in seconds: 5, 10, or 15"
  2. Changed1 schema field changed
    • addedInput schema / properties / monitor_consent
      Added value: +{
      +  "description": "Enable or disable the weekly Consent Scan, which records the cookies the page sets before and after consent (http/keyword only, counts toward the plan's Consent Scan limit). Reports observations, never a compliance verdict.",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / accepted_status_codes
      Added value: +{
      +  "description": "HTTP monitors only: status codes 400-599 (at most 10) to count as up in addition to 200-399, for a URL that answers 401, 404 or 503 on purpose. Send an empty array to clear the list. Not available for keyword monitors.",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / private_location_id
      Added value: +{
      +  "description": "UUID of one of your own Private Locations to check this monitor from instead of the Baromio fleet. Use list-private-locations for valid values. Only http, keyword, and tcp types are eligible.",
      +  "type": "string"
      +}
  5. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With only openWorldHint=true in annotations, the description usefully adds the auth requirement (Full Access MCP token) and plan eligibility, which the annotations do not convey. However, for a 22-parameter update it never states whether this is a partial patch (omitted fields preserved) or a full replace, nor what happens if `type` is changed, which are the behavioral facts an agent most needs.

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?

Three short sentences, front-loaded with the action and resource, then scope, then prerequisites. No filler; only the missing heartbeat type keeps it from being fully tight.

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 mutation tool with 22 optional parameters, no output schema, and minimal annotations, key facts are absent: partial vs full update semantics, whether type changes are permitted, and what the response contains. The auth/plan prerequisites and type scope cover the basics but leave real gaps.

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 every parameter including enums, timeout values, and region/location lookups is already documented. The description adds nothing parameter-specific beyond naming monitor types, and it actually omits 'heartbeat' even though heartbeat appears in the type enum, creating a small mismatch.

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?

States a specific verb and resource ('Update a monitor by ID') and scopes the supported monitor types, so an agent immediately knows this modifies an existing monitor rather than creating one. It does not name or differentiate against overlapping siblings such as pause-monitor, set-alert-threshold, or create-monitor, which also touch monitor config.

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?

'Update a monitor by ID' plus the prerequisite sentence ('Requires Full Access MCP token and eligible paid plan') implies when the tool is callable, but there is no explicit guidance on when to use this versus set-alert-threshold or pause-monitor/resume-monitor, which overlap with the alert_threshold and notification parameters here.

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