Skip to main content
Glama

Get project health

runheed_get_project_health
Read-only

Returns a 0 to 100 health score for a project (or the whole workspace), errors in the last 24 hours, the unresolved count, the error rate, recent issues and recommendations.

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

Input Schema

NameRequiredDescriptionDefault
projectIdNoProject id or slug (e.g. shop-api); all projects if not specified

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (uses default if not specified)"New value: +"Project id or slug (e.g. shop-api); all projects if not specified"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds real behavioral detail: the 0-100 score scale, the fixed 24-hour error window, and the full set of returned sections. It omits any note on aggregation lag or how recommendations are generated, but that is a minor gap given the annotation coverage.

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 front-loaded sentence that names the primary output first and then enumerates the secondary sections. No filler, no restatement of the title.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing return values, and it does so by listing the six sections an agent will receive. It leaves the exact shape of 'recent issues' and 'recommendations' undefined, which would help an agent decide how to consume the response.

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

Parameters3/5

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

Schema coverage is 100% and the single optional projectId is already documented as 'Project id or slug; all projects if not specified'. The description's '(or the whole workspace)' corroborates the omission behavior but adds no format or example detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Returns a 0 to 100 health score for a project (or the whole workspace)') and enumerates what comes back: errors in last 24h, unresolved count, error rate, recent issues, recommendations. This clearly separates it from siblings like runheed_get_error (single error), runheed_get_recent (raw feed) and runheed_get_trends (time series).

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?

Usage is only implied by the content: an agent can infer this is the overview/dashboard call rather than a drill-down. There is no explicit guidance on when to prefer it over runheed_get_recent or runheed_get_trends, nor when to drill into runheed_get_error afterwards.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.