checkly_list_check_statusesList the current pass/fail/degraded status of every check — the 'what's down right now' view. Public API: GET /v1/check-statuses.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so agent knows it's safe. Description adds API endpoint and status types (pass/fail/degraded), providing useful behavioral context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero waste. First sentence states core action, second provides API endpoint. Front-loaded with essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Description is adequate for a zero-parameter tool. It covers what is listed and the API method. Could be enhanced by clarifying response format, but not required for basic understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters; schema description coverage is 100% trivially. Baseline 4 is appropriate as description adds no parameter info but none is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it lists current pass/fail/degraded status of every check. Uses specific verb 'list' and resource 'check statuses'. Distinguishes from sibling tools like checkly_get_check_status (single check) and checkly_list_checks (check configurations).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear context as 'what's down right now' view, implying immediate status overview. Does not explicitly state when not to use, but the purpose is self-evident given zero parameters and clear sibling differentiation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct resources (checks, groups, results, statuses, etc.). However, `checkly_get_check_alerts` vs `checkly_list_check_alerts` could be confused, though descriptions help clarify per-check vs account-level.
All tools follow a consistent `checkly_verb_noun` pattern, using `get`, `list`, and `create` appropriately. No mixing of styles.
22 tools cover a broad monitoring domain reasonably well, but a few resource types (e.g., dashboards, snippets, runtimes) with only list operations may be underutilized.
The tool set is heavily read-only; only maintenance windows and variables have create operations. Missing create/update/delete for checks, groups, alert channels, and other core resources, limiting agent ability to manage the account.