Skip to main content
Glama
depsdev-mcp

depsdev-mcp

by Ankur1911

project_health

Read-onlyIdempotent

Evaluate a source repository's health using stars, forks, open issues, licence, and OpenSSF Scorecard results, with weak checks listed first.

Instructions

Health of a source repository: stars, forks, open issues, licence and the OpenSSF Scorecard overall score. By default lists only the checks that scored below 10, weakest first.

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": {
      "project_id": "<project_id>"
    },
    "name": "project_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
all_checksNoInclude every scored check, not just the weak ones.
project_idYesSource project id such as 'github.com/expressjs/express' (GitHub, GitLab or Bitbucket).

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 establish readOnly, idempotent, and open-world behavior, so the bar is lower. The description still adds real value by disclosing the default filtering rule (only checks scoring below 10) and the ordering (weakest first), which an agent cannot infer from the annotations.

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 sentences, no filler: the metric list comes first, followed by the default-behavior caveat that would otherwise surprise an agent. Every clause carries information.

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 explaining return content, and it does so by enumerating the reported metrics. The only gap is not clarifying whether per-check details (names/individual scores) accompany the overall Scorecard score when all_checks is set.

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%, so both parameters are already documented, and the all_checks description already explains the weak-vs-all distinction. The description's only addition is the concrete 'below 10' threshold and 'weakest first' ordering, which is marginal 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 names a specific resource (source repository) and enumerates exactly what it reports: stars, forks, open issues, licence, and OpenSSF Scorecard overall score. That content set distinguishes it from siblings like project_packages or advisory without needing to name them, though no sibling is explicitly referenced.

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: an agent can infer this is the tool for repo-level health/scorecard metrics, but there is no explicit 'use this when...' statement, no exclusions, and no guidance about when a different tool (e.g. dependencies or advisory) would be more appropriate.

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