Skip to main content
Glama

StatusCake MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Update an uptime check

statuscake_update_uptime_check
Destructive

Change an uptime check's settings. Only the fields you pass are changed; list fields (tags, contact_groups, regions, dns_ips) are REPLACED, and an empty list clears them. Pass paused=true to pause a check and paused=false to resume it. StatusCake: PUT /uptime/{test_id}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoName of the hosting provider (informational).
nameNoNew name for the check.
portNoDestination port (TCP, SMTP, SSH checks).
tagsNoTags for the check. An empty list clears them.
pausedNotrue to pause the check (stops running and alerting), false to resume.
dns_ipsNoIP addresses the DNS record must resolve to (DNS checks).
regionsNoRegion codes to run the check from (see statuscake_list_uptime_locations).
test_idYesThe uptime check id.
timeoutNoSeconds to wait for the first byte, 5-75 (default 15).
use_jarNoEnable cookie storage between requests.
post_rawNoRaw HTTP POST body to send.
post_bodyNoJSON object string submitted with the request; setting it makes the check use HTTP POST.
check_rateNoSeconds between checks: 0, 30, 60, 300, 900, 1800, 3600 or 86400.
dns_serverNoNameserver to query (DNS checks).
user_agentNoCustom User-Agent sent with each check.
do_not_findNoInvert find_string: the check is down if the string IS present.
find_stringNoString to look for in the response; the check is down if not found.
website_urlNoNew URL, FQDN or IP address to check.
confirmationNoNumber of confirmation servers that must agree before alerting, 0-3 (default 2).
trigger_rateNoMinutes to wait before sending an alert, 0-60 (default 0).
custom_headerNoJSON object string of headers to send, e.g. {"X-Env":"prod"}.
basic_passwordNoHTTP basic-auth password for the target.
basic_usernameNoHTTP basic-auth username for the target.
contact_groupsNoContact group ids to alert (see statuscake_list_contact_groups). An empty list clears them.
final_endpointNoWhere the redirect chain should end (with follow_redirects).
include_headerNoInclude response headers in the find_string search.
enable_ssl_alertNoAlert when the site's SSL certificate is about to expire.
follow_redirectsNoFollow redirects when testing (off by default).
status_codes_csvNoComma-separated HTTP status codes that count as down, e.g. "500,502,503".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only supply destructiveHint=true, and the description goes well beyond that by disclosing the exact destructive nuance: list fields (tags, contact_groups, regions, dns_ips) are REPLACED and an empty list clears them. It also explains the paused toggle semantics, which is critical to avoid accidentally disabling alerting.

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?

Three short sentences plus an endpoint reference, with the core partial-update rule front-loaded before the list-replacement warning. No filler or repetition of schema content.

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 29-parameter destructive mutation with no output schema and full schema coverage, the description covers the highest-risk behaviors (list replacement, pause toggle). It omits permissions/auth requirements and any indication of the response, which would be nice but is not essential here.

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 description coverage is 100%, so the baseline is 3, but the description adds cross-parameter semantics the schema does not state—the replace-on-write behavior for regions and dns_ips (schema only mentions clearing for tags/contact_groups) and the pause/resume meaning of paused.

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 ("Change an uptime check's settings") and even names the underlying API call ("StatusCake: PUT /uptime/{test_id}"). The verb "Change" implicitly separates it from the create/get/list siblings, but no sibling is named explicitly, so it stops short of full differentiation.

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?

Gives clear operational context: only passed fields change, list fields are replaced wholesale, and paused=true/false toggles the check state. However, it never says when to prefer this over siblings (e.g. fetching the check first with statuscake_get_uptime_check) or any prerequisite/precondition for calling it.

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

All StatusCake MCP by usefulapi 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