Skip to main content
Glama
Codemend

Codemend MCP Server

by Codemend

codemend_project_health

Check the health and status of your Codemend monitoring setup to ensure production error tracking functions correctly.

Instructions

Check the health and status of your Codemend monitoring setup

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the 'codemend_project_health' tool, which registers the tool and defines its handler to perform a GET request to '/api/health'.
    server.tool(
      "codemend_project_health",
      "Check the health and status of your Codemend monitoring setup",
      {},
      async (): Promise<ToolResult> => {
        try {
          const apiKey = getApiKey();
          const res = await apiRequest<unknown>("GET", "/api/health", apiKey);
    
          if (!res.ok) {
            const msg =
              typeof res.data === "object" && res.data !== null && "error" in res.data
                ? String((res.data as Record<string, unknown>).error)
                : `HTTP ${res.status}`;
            return errResult(msg);
          }
    
          return okResult(res.data);
        } catch (err) {
          return errResult(err instanceof Error ? err.message : String(err));
        }
      }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to specify what health metrics are verified (connectivity, configuration, permissions), the return format, or whether the operation is read-only.

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 consists of a single, efficient 9-word sentence that front-loads the action verb. There is no redundant or wasted text given the simplicity of the tool.

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?

While appropriately brief for a zero-parameter tool, the description lacks information about return values or output structure in the absence of an output schema. It adequately conveys the high-level purpose but leaves operational specifics undocumented.

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 accepts zero parameters, establishing a baseline of 4. With no arguments to document and 100% schema coverage trivially satisfied, no additional parameter semantics are required from the description.

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 uses a clear specific verb ('Check') and identifies the resource ('health and status of your Codemend monitoring setup'). It implicitly distinguishes from fix-oriented siblings (apply_fix, copy_fix, etc.) by focusing on health/status rather than remediation.

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?

The description provides no guidance on when to invoke this tool versus alternatives. It does not indicate whether this should be called before error remediation, how often to poll it, or what constitutes a healthy versus unhealthy state.

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/Codemend/mcp'

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