healthchecksio_list_integrationsList the project's notification integrations ("channels") — {channels:[{id, name, kind}]}. The ids are what you assign to a check's channels field. Healthchecks: GET /channels/.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already declares this is safe and non-destructive. The description adds meaningful behavioral detail beyond the annotation: it states the exact response shape, explains the semantics of the ids, and references the underlying Healthchecks GET endpoint. No contradiction with the annotation exists.
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 compact and front-loaded with the primary action and object. It packs the response shape, the practical significance of the ids, and the underlying endpoint into two tight sentences with no filler.
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?
For a parameterless, read-only listing tool, the description is complete: it identifies the resource, states the output format, clarifies how the output should be used, and there is no output schema requiring additional return-value documentation. No important calling information is missing.
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?
The input schema has zero parameters, so there is nothing for the description to explain about parameters. The baseline for a parameterless tool is 4, and the description appropriately focuses on the output rather than inventing parameter guidance.
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 uses a specific verb ('List') and a clear resource ('the project's notification integrations'), immediately clarifying what the tool does. It distinguishes this from sibling tools like list_checks, list_badges, and list_pings by explicitly framing the resource as 'channels' rather than checks, badges, or pings.
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?
The description gives clear usage context: the returned ids are what you assign to a check's `channels` field. This tells the agent when this tool is relevant. It does not explicitly state when not to use it or name alternatives, but for a simple read-only list tool that is a minor omission.
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.
Each tool maps to a distinct resource and action: check CRUD, pause/resume, pings, flips, badges, and integrations. The only potentially related pair, list_pings and get_ping_body, is clearly separated by metadata vs raw body.
All tools follow a clean verb_noun snake_case pattern, with list_* for collections and get_/create_/update_/delete_/pause_/resume_ for single-resource actions. There are no mixed casing styles or inconsistent verb choices.
12 tools is well within the ideal range for this domain, and each tool covers a distinct, necessary operation for managing and inspecting Healthchecks monitoring. The set feels complete without being bloated.
The check lifecycle is fully covered with create, get, update, delete, pause, and resume, plus history and supporting data like pings, flips, badges, and integrations. The main minor gap is that there is no tool to send a ping or manually trigger a check success/failure, so end-to-end ping verification must happen out-of-band.