Skip to main content
Glama
ni-c

healthchecks-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get instance status

get_status
Read-onlyIdempotent

Verify that the Healthchecks instance is reachable and its database responds without requiring an API key. Use it first when issues arise.

Instructions

Checks that the configured Healthchecks instance is reachable and its database is answering. Needs no API key, so it is the tool to try first when something is not working.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue only when the answer was exactly "OK".
answerYesUp to 4 kB of whatever replied.
sourceNo
instanceYes
untrustedNoPresent only when the instance answered something else.
control_characters_removedNoPresent only when the answer carried any.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedOutput schema / properties / control_characters_removed
      Added value: +{
+  "description": "Present only when the answer carried any.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
  2. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare the tool as read-only, idempotent, and non-destructive, and the description aligns with these attributes. It adds the extra behavioral detail that no API key is needed, which is not covered by the annotations. This transparency helps the agent understand the tool's side-effect profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured, consisting of two sentences. The first sentence states the core function, and the second provides usage context. No unnecessary words or redundancy are present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description provides sufficient context for an agent to know when and why to call this tool, including the fact that it requires no API key and is ideal for initial troubleshooting. Since the output schema is defined separately, the description does not need to cover return values. It is complete for effective selection and invocation.

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?

The schema has no parameters (empty properties), so parameter coverage is trivially complete. With no parameters to describe, the description cannot add further semantic detail. The baseline of 3 is appropriate since there is nothing to explain beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: checking the reachability of the configured Healthchecks instance and its database. The verb 'checks' is specific and the resource is well-defined. It also implicitly differentiates itself from sibling tools that perform data operations rather than health checks.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use the tool: 'try first when something is not working'. It also notes that no API key is required, which helps an agent decide to use this tool as a preliminary diagnostic step before trying others that may need authentication.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools