Skip to main content
Glama

health

Check project health across server, git, documentation, definition of done, and CI/CD workflows with status metrics and task creation.

Instructions

[HINT: Health check. action=server|git|docs|dod|cicd. Status and health metrics.]

Unified health check:

  • action="server": Server operational status, version

  • action="git": Working copy health, uncommitted changes, sync status

  • action="docs": Documentation health score, broken links

  • action="dod": Definition of done validation for task completion

  • action="cicd": CI/CD workflow validation, runner config

📊 Output: Health status and metrics 🔧 Side Effects: Creates tasks (docs action with create_tasks=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoserver
agent_nameNo
check_remoteNo
output_pathNo
create_tasksNo
task_idNo
changed_filesNo
auto_checkNo
workflow_pathNo
check_runnersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description partially discloses behavioral traits like side effects ('Creates tasks for docs action') and output format. However, it lacks details on destructive actions, authorization, or rate limits.

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

Conciseness4/5

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

The description is concise, front-loaded with a HINT, and uses bullet points for action options. Every sentence adds value, though the emoji and formatting could be streamlined for machine parsing.

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?

Given 10 parameters and 0% schema coverage, the description fails to cover most parameters. The output schema exists, but the description does not leverage it. The tool's purpose is clear, but parameter details are insufficient.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only explains the 'action' parameter's values. The other 9 parameters (agent_name, check_remote, etc.) are not described, leaving the agent uninformed about their usage.

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 defines the tool as a unified health check with specific actions (server, git, docs, dod, cicd). It uses a specific verb ('check') and resource ('health status/metrics'), distinguishing it from sibling tools like automation or context.

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

Usage Guidelines3/5

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

The description implies usage for health checking but provides no explicit guidance on when to use this tool vs alternatives. Sibling tools are not mentioned, and no criteria like 'use this before running other tools' are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidl71/project-management-automation'

If you have feedback or need assistance with the MCP directory API, please join our Discord server