Skip to main content
Glama

Is it ready to launch? Score a repo, npm package or website

scbee_score
Read-onlyIdempotent

Check whether a GitHub repo, npm package or website is ready to launch or publish, and whether other AI agents can use it. Returns a 0-100 launch readiness score (plus an Agent-Ready score for repos), the reason for every point, and a checklist of fixes for what is missing, biggest wins first. Use before launching, publishing, announcing or sharing a project, when asked what to fix before shipping, or to judge whether a dependency looks maintained. Fixed rules on public data, no AI. Not for private repos, and not a code-quality or security review.

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": "<project>"
    },
    "name": "scbee_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesgithub.com/owner/repo, owner/repo, an npm package name (or npm:name), or a website like example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds meaningful context beyond that: results are computed on public data with fixed rules and no AI, and the output ordering is 'biggest wins first'. It does not mention latency, rate limits, or what happens when a project is not found, which are the remaining behavioral gaps.

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?

Purpose is front-loaded in the first clause, outputs come second, usage triggers third, and exclusions last — a well-ordered funnel. Three sentences with no repeated or filler content despite covering a lot of ground.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 return-value burden and does so: score range, the repo-specific secondary score, the reasoning payload, and the shape of the fix list. Combined with annotations covering side effects and a fully documented single parameter, an agent has everything needed to call and interpret this tool correctly.

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% and the single 'project' param already enumerates the accepted formats (github.com/owner/repo, owner/repo, npm name, npm:name, example.com). The description adds only one constraint beyond the schema — that private repos are unsupported — so it sits at the baseline rather than enriching semantics.

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 (check/score) over three concrete resource types (GitHub repo, npm package, website) and names the exact outputs: a 0-100 launch readiness score, an Agent-Ready score for repos, per-point reasons, and a prioritized fix checklist. No sibling (find_complements, handoff, project_card, search_agents) does scoring, so the agent can separate this tool without opening another schema.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions — before launching, publishing, announcing or sharing a project, when asked what to fix before shipping, or to judge whether a dependency looks maintained. It also names exclusions: not for private repos, and not a code-quality or security review, which prevents misrouting.

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.