Skip to main content
Glama

Macpilot Health

macpilot_health

Check server health across domains to verify macpilot-mcp service status and identify availability issues.

Instructions

Server health across domains.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "macpilot_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden and delivers nothing: no disclosure of whether the call is read-only, what permissions are needed, latency, rate limits, or what 'domains' implies about coverage. The only behavioral signal is the word 'health', which is too thin for a zero-annotation definition.

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

Conciseness3/5

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

A single short sentence is front-loaded and wastes no words, but at this length the terseness is under-specification rather than efficiency. It gives no hook an agent can act on beyond the word 'health'.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but with no annotations and no parameter detail the agent still lacks the basics: what domains are covered, whether this is a safe read, and when to call it. The definition is too thin for a no-annotation, no-input diagnostic tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is moot for an empty object.

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

Purpose2/5

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

"Server health across domains" essentially restates the name and title (Macpilot Health) without a specific verb or scope. It never says what is measured (uptime, status per service, quota) or what a 'domain' is, so an agent cannot distinguish this from a generic status probe.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of any alternative or follow-up. Given siblings are mail/calendar/contacts tools, there is no hint that this is the diagnostic entry point for a failing mail operation versus a standalone check.

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