Skip to main content
Glama

codebuddy_health

Verifies that the CodeBuddy Code HTTP service for the personal-developer transport is reachable and healthy, helping diagnose connectivity before dispatching development tasks.

Instructions

Check the CodeBuddy Code HTTP service used by the personal-developer transport.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the scope of the check (the HTTP service backing the personal-developer transport), which is genuinely useful context. However it does not say whether the call is side-effect free, whether it can be slow or time out, or what a negative result looks like. For a zero-parameter probe the risk is low, so a middle score is fair.

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?

A single sentence with no redundant clauses, and the resource being checked is foregrounded. Nothing could be removed without losing 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?

With no output schema and no annotations, the description should explain what a health result conveys (boolean up/down, service metadata, error shape), and it does not. It is adequate to identify the tool but leaves the agent guessing about the return value, which is the one remaining burden for a probe 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. The baseline for a no-parameter schema is 4, and nothing in the description misleads about inputs.

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?

States a specific verb ('Check') and a specific resource ('the CodeBuddy Code HTTP service'), so the agent knows this is a health probe rather than a job or message operation. It falls short of a 5 because 'check' is ambiguous about what is verified (reachability vs. readiness vs. version), and it does not contrast itself with codebuddy_job_status or clawbridge_status.

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?

There is no statement of when to call this versus the sibling status tools, no mention of preconditions, and no indication of what to do on failure. The only guidance is implicit in the word 'Check', which the scoring rubric rates as barely above none.

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