checkly_list_check_alertsList recent alert notifications fired across the whole account. Public API: GET /v1/check-alerts.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | End of range as a Unix timestamp (seconds). | |
| from | No | Start of range as a Unix timestamp (seconds). | |
| page | No | 1-based page number. | |
| limit | No | Page size. |
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?
The annotation readOnlyHint=true already indicates safe read-only behavior. The description adds the API endpoint detail and implies recency but does not elaborate on sorting, rate limits, or pagination behavior. Given annotations carry the safety disclosure, the description provides minimal additional behavioral context.
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?
The description is two sentences, directly stating purpose and API endpoint. It is front-loaded and concise, with no filler. Minor improvement could be omitting the API path as it adds limited value for an agent.
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?
The description omits details about the output format, pagination behavior, and how 'recent' is defined. Since there is no output schema, the description should compensate but fails to provide sufficient context for a complete understanding of the tool's behavior.
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?
All four parameters have complete descriptions in the schema (100% coverage). The tool description itself adds no additional parameter meaning beyond the schema, hence baseline score of 3 is appropriate.
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?
The description clearly states the verb 'list' and the resource 'alert notifications' with explicit scope 'across the whole account', distinguishing it from checkly_get_check_alerts which is scoped to a specific check. The tool name and title are also well aligned.
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?
No guidance on when to use this tool versus alternatives like checkly_get_check_alerts. The description does not mention prerequisites, context, or exclusions, leaving the agent to infer usage without explicit direction.
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.