Skip to main content
Glama

StatusCake MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Create an uptime check

statuscake_create_uptime_check
Destructive

Start monitoring a URL, host or IP. Returns the new check's id as data.new_id. Faster check rates and some regions depend on the plan. StatusCake: POST /uptime.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoName of the hosting provider (informational).
nameYesName of 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).
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.
test_typeYesCheck type: HTTP, HEAD, TCP, DNS, SMTP, SSH or PING.
check_rateYesSeconds 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_urlYesURL, 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

B3.2/5.0
Behavior3/5

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

With no output schema, calling out 'Returns the new check's id as data.new_id' adds real value about the response. It also flags plan-gated check rates and regions. However, it does not explain the destructiveHint creation semantics or the fact that many of the 29 params are conditionally relevant by test_type.

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?

Four short sentences with the core action front-loaded and no padding. The trailing 'StatusCake: POST /uptime' is arguably internal detail but is cheap and confirms the creation endpoint.

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 29-parameter creation tool with no output schema, the description covers the return value and plan constraints reasonably. It does not clarify which parameters apply to which test_type, leaving a notable gap given the tool's complexity.

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%, and each parameter is already documented in the schema, including enums for check_rate and test_type. The description's 'URL, host or IP' loosely echoes website_url but adds no meaning beyond the schema, so the baseline of 3 applies.

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 description states a concrete verb and resource: 'Start monitoring a URL, host or IP,' which is specific enough to be actionable. The tool name 'uptime_check' distinguishes it from the heartbeat and ssl sibling creators, though the description itself never explicitly names those alternatives.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance or comparison to sibling creators like statuscake_create_heartbeat_check or statuscake_create_ssl_check. The only usage-adjacent note is that 'faster check rates and some regions depend on the plan,' which is a constraint rather than guidance on choosing this tool.

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