Skip to main content
Glama

Is this project alive?

repo_health
Read-onlyIdempotent

Check whether a GitHub project is active by measuring recent human PR merges, commits, merge times, open counts, and latest release before starting work.

Instructions

Is the project alive? PRs merged in 90 days (bots excluded), human authors, commits, weekly merges, median time to merge, open counts, latest release. 2 requests signed in, ~7 anonymous.

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": {
      "repo": "<repo>"
    },
    "name": "repo_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesowner/name or a github.com URL
forceNoBypass the cache (costs requests)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: bots are excluded, the window is a fixed 90 days, and the call has a quantified cost (2 requests signed in, ~7 anonymous), which explains why 'force' bypassing the cache matters.

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?

Two short blocks: a front-loaded framing question followed by a dense metric list and a cost note. Every clause carries information about scope or cost, and nothing is padded.

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 correctly takes on the burden of describing what comes back by enumerating the metrics. The 90-day window, bot exclusion and request cost round it out; only the response shape/aggregation details (e.g. how 'weekly merges' is structured) remain unspecified, which is a minor gap.

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 description coverage is 100% — 'repo' documents the owner/name or URL form and 'force' documents cache bypass with a cost note — so the baseline is 3. The description's mention of request cost reinforces the 'force' tradeoff but adds no new syntax or format detail beyond the schema.

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 enumerates exactly what the tool returns — PRs merged in 90 days excluding bots, human authors, commits, weekly merges, median time to merge, open counts, latest release — so the resource is unmistakable. It is clearly a repo-level liveness/activity reporter, distinguishable in substance from a 'contribution_brief' or 'team_responsiveness' sibling, though it never names an alternative directly.

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?

The leading question 'Is the project alive?' implies the use case (assessing project activity/vitality), which is enough to infer intent. However, there is no explicit when-to-use, when-not-to-use, or routing to the closely related siblings like contribution_brief or team_responsiveness.

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