Skip to main content
Glama

merjax_repo_health

Read-only

Compute the current health report for a public repo: overall score (0-100), letter grade, per-category breakdown (security/testing/complexity/dependencies/documentation/activity), and a list of insights to fix next. Backed by computeHealthScore in src/lib/intelligence.ts.

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

Input Schema

NameRequiredDescriptionDefault
repoYesRepo name
ownerYesRepo owner — username or organisation slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the result is a freshly computed report with a defined structure and names the backing function, which gives a sense of determinism, but says nothing about latency, caching, cost, or whether the repository must be public and reachable.

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?

A single dense sentence front-loads the action and the return shape, with zero filler. The trailing 'Backed by computeHealthScore in src/lib/intelligence.ts' is an internal implementation detail that earns little for an agent deciding whether to call the tool.

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?

Because there is no output schema, the description carries the burden of describing returns and does so well: score range, letter grade, six named categories, and actionable insights. What is missing is behavior around failures, freshness of the 'current' computation, and any cost or permission requirement.

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% with only two required params (owner, repo), so the baseline is 3. The description's only added semantic is that the repo must be public, a constraint not present in the schema, but it offers no format examples or edge-case notes (private repos, renamed owners).

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 names a specific verb ('compute') and resource ('health report for a public repo') and enumerates the report's contents (score 0-100, letter grade, per-category breakdown, insights). It is clear what the tool does, but it never distinguishes itself from closely related siblings such as merjax_repo_rating, merjax_ci_health, or merjax_explain_repo, which an agent could plausibly choose instead.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'public repo' implicitly constrains scope, but the description gives no condition that selects this tool over merjax_repo_rating or merjax_ci_health, and no prerequisites (auth, rate limits, analysis time) are mentioned.

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.

Resources