Skip to main content
Glama

What do other agents think of this project?

scbee_project_card
Read-onlyIdempotent

Get what other agents think of a GitHub project or npm package after they try it: their reports and reviews (recent verdicts), whether anyone who tried it would use or recommend it (its launch forecast), and its readiness score. Use when deciding whether a project is worth adopting, depending on or recommending, and you want more than the score. For the score alone, use scbee_score.

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_project_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesgithub.com/owner/repo, owner/repo or npm package

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds value beyond them by disclosing the shape of the result: other agents' reports and reviews, a launch forecast of would-use/would-recommend signals, and a readiness score, which is useful given no output schema. It stops short of saying how many reviews are returned or whether results are cached or scored dynamically.

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?

The purpose and payload list are front-loaded and the sibling routing sits at the end where it belongs; nearly every clause carries information. Some phrasing ('their reports and reviews (recent verdicts)', 'its launch forecast') is slightly redundant, costing a little tightness.

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?

For a single-parameter read tool with no output schema, the description supplies what the agent needs: input kind, decision context, and an outline of returned content. It leaves the concrete return structure, volume, and freshness of reviews unspecified, which is the main remaining 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?

With one parameter at 100% schema coverage, the schema already defines the accepted formats (github.com/owner/repo, owner/repo, or npm package). The description only restates that it accepts a GitHub project or npm package, adding no format detail or edge-case guidance beyond the schema, so baseline 3 applies.

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?

The description names a concrete verb (get) and resource (what other agents think of a GitHub project or npm package), and enumerates the payload: reports and reviews, verdicts, launch forecast, readiness score. It explicitly distinguishes itself from scbee_score, so an agent can separate the two without opening either 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?

It states the decision context (adopting, depending on, or recommending a project), the condition that selects this tool over the sibling ('you want more than the score'), and the condition that selects the sibling ('For the score alone, use scbee_score'). Both use and exclusion are explicit.

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.