Skip to main content
Glama

Get Repo Health

get_repo_health

Fetch maintenance and responsiveness health metrics for a GitHub repository in owner/repo format to verify project activity before adopting or generating code.

Instructions

Fetch in-depth maintenance and responsiveness health metrics for a specific GitHub repository.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "full_name": "<full_name>"
    },
    "name": "get_repo_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
full_nameYes'owner/repo' format (e.g., 'pyannote/pyannote-audio').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
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 disclosure burden. It implies a read-only lookup and names the metric categories (maintenance, responsiveness), but says nothing about authentication needs, rate limits, latency, or whether results are cached/live. Return values are covered by the output schema, which limits the gap somewhat.

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?

One tight sentence with the key qualifier ('in-depth maintenance and responsiveness') front-loaded. No wasted words, though 'in-depth' is a generic filler that could be replaced with concrete metric categories.

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?

For a simple one-parameter read tool with an output schema and full schema coverage, the description is minimally adequate. However, it never enumerates what 'health metrics' include (commit cadence, issue response time, etc.) or how they differ from other repo tools, leaving an agent to open the schema to understand the output.

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?

There is a single parameter with 100% schema description coverage including the 'owner/repo' format and an example, so the schema already does the work. The description adds no additional meaning about the parameter, which is acceptable given the high coverage baseline.

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 ('Fetch') and resource ('maintenance and responsiveness health metrics for a specific GitHub repository'). It is clearly distinguishable from sibling tools like search_github_repos or get_readme, though it never explicitly contrasts itself with them.

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 gives no guidance on when this tool should be chosen over siblings such as search_github_repos, get_readme, or compare_candidates. The phrase 'for a specific GitHub repository' hints at scope but provides no when-to-use or when-not-to-use conditions.

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