Get the live status of a Cronping check (up/down/new, last ping time, ping count, and whether an alert channel is set).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| claim_token | Yes | The claim_token returned by create_heartbeat. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is known. The description adds behavior context by enumerating the returned information (up/down/new, last ping time, ping count, alert channel), which is valuable since there is no output schema. However, it does not mention error or edge-case behavior.
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 a single, compact sentence that front-loads the action and then lists the exact data returned. Every word adds value.
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?
Despite the lack of an output schema and only partial parameter documentation, the description conveys the tool's purpose and return data adequately. Given the tool's simplicity and the annotations confirming read-only/idempotent behavior, it is reasonably complete for an agent to select. However, the ambiguity around the 'id' parameter prevents a 5.
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?
Schema description coverage is only 50% (claim_token has a description, id does not). The tool description does not explain the parameters at all, leaving the meaning of 'id' ambiguous. While claim_token is documented in the schema, the missing id description is not compensated.
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 tool's action ('Get the live status') and resource ('Cronping check'), and distinguishes it from sibling tools like create_heartbeat and set_heartbeat_alert by focusing on reading status rather than modifying or creating.
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 implies usage for retrieving current status but does not explicitly state when to choose this over alternatives or provide exclusions. The context signals show sibling tools for creation and alerting, but the description lacks direct comparison.
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 has a clearly distinct role: create, delete, status check, bulk import from crontab, pause/resume, ping, and alert configuraiton. No two tools appear to perform the same action, and the descriptions reinforce their separation.
Tool names consistently follow a verb_noun snake_case pattern (create_, delete_, pause_, ping_, set_). 'import_crontab' deviates slightly by naming the input format rather than the domain object, but it remains readable and fits the verb-based convention.
Seven tools is well within the ideal range for a focused heartbeat-monitoring server. Each tool represents a necessary operation without bloat or redundant overlap.
The core lifecycle is covered: create, ping, pause/resume, alert setup, status, delete, and bulk import. Missing update functionality for period/grace and no list-all-heartbeats operation are notable but non-blocking gaps for the core dead-man's-switch workflow.