Skip to main content
Glama

starproof_score

Score a GitHub repository's authenticity: pulls the repo through the GitHub API and checks the fake-star / astroturf fingerprint (stars-vs-forks, star velocity, missing language/license, product-named org, keyword-stuffed topics, hype description). Returns a 0-100 authenticity score, a verdict (likely-authentic/suspicious/likely-faked) and the evidence list. Free, no key. For unthrottled use, GET /x402/score?repo=owner/name is the paid per-check authenticity receipt ($0.01 via x402, USDC on Base; no rate limit, no signup).

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

Input Schema

NameRequiredDescriptionDefault
repoYesowner/name or a full github.com URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the upstream dependency (GitHub API pull), the output shape (0-100 score, verdict enum, evidence list), the cost model (free, no key) and the existence of throttling. It stops short of stating rate-limit magnitude, error behavior for invalid/private repos, or latency, which are the remaining unknowns for a network-backed tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are well front-loaded and dense with useful signal. The final sentence, however, is a long pricing/payment digression (x402, USDC on Base, no signup) that does not help invoke this tool and risks steering the agent toward a raw HTTP call instead of 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?

There is no output schema, so the description must explain returns — and it does, specifying the score range, the three verdict values, and the evidence list. Combined with the documented heuristics, an agent has enough to call it and interpret results; only failure modes and rate-limit specifics are absent.

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 'repo' parameter is already documented as 'owner/name or a full github.com URL'. The description only echoes the format via the 'repo=owner/name' URL example, adding no new meaning; baseline 3 applies when the schema does the heavy lifting.

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 ('Score a GitHub repository's authenticity') and then enumerates the exact signals checked (stars-vs-forks, star velocity, missing language/license, product-named org, keyword-stuffed topics, hype description). An agent knows precisely what this does without opening the schema, and the only sibling (starproof_health) is not a plausible substitute for a scoring call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating context ('Free, no key') and names an alternative route for unthrottled use (the paid x402 endpoint). What's missing is guidance on when NOT to call it, e.g. rate-limit failure behavior or what to do if the repo doesn't exist; and the paid endpoint is described as an HTTP path rather than a separate tool, which leaves the agent slightly unsure whether it should switch tools or issue a raw request.

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