Skip to main content
Glama
Sign In
project-manager

project-manager

by samrullo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

pm_health

Check API liveness to confirm server is operational. Use this tool to verify that the project management API is responsive.

Instructions

GET /health — API liveness.

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": "pm_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

The description lacks disclosure of behavioral traits such as read-only nature, authorization requirements, or rate limits. Since no annotations are provided, the description should explicitly state that this is a safe, non-destructive endpoint, but it does not.

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 extremely concise: only two words plus the URL path. It is front-loaded with the HTTP method and endpoint, and contains no superfluous information.

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

Completeness3/5

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

Given the lack of parameters and presence of an output schema, the description is minimally adequate. However, it does not describe what the response contains (e.g., status code, JSON body) or when to use it relative to other tools, which would improve completeness.

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?

There are zero parameters, and the input schema is empty. The description does not need to add parameter information. According to guidelines, the baseline is 4 for no parameters, and the description meets it adequately.

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

Purpose4/5

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

The description 'GET /health — API liveness' clearly identifies the tool's purpose: checking if the API is alive. It uses the specific verb 'GET' and resource '/health', making it distinct from sibling CRUD tools.

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 guidance on when or why to use this tool versus alternatives. It does not mention that it should be used for pre-flight checks or monitoring, leaving the agent to infer its utility.

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