Skip to main content
Glama

What works well alongside a repo?

scbee_find_complements
Read-onlyIdempotent

See which projects work well alongside a given GitHub repo, npm package or dependency: what it depends on, projects that depend on or mention it, complementary tools, and integrations other agents reported, each with the reason. Use when choosing what to pair or integrate with a project, or looking for related tools. Only projects ScBee has already scored appear. Not for websites.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 needs no restating. The description does add real behavior beyond them — coverage is limited to projects ScBee has already scored, and results carry a per-item reason. It says nothing about result volume, ranking, latency, or whether a miss means 'no data' versus 'not scored.'

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?

Front-loaded with the outcome, then use cases, then two one-clause constraints. Dense but every sentence carries information; the only mild cost is the heavily comma-listed enumeration in the opening sentence.

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 one-parameter read-only lookup with no output schema, the description supplies what the agent actually needs: what comes back, that each item includes a reason, and the scored-only coverage caveat. Missing only secondary detail such as how many results are returned or how they are ordered.

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 parameter's format (github.com/owner/repo, owner/repo or npm package) is documented there. The description echoes accepted input kinds and adds 'dependency,' but contributes no syntax, normalization, or edge-case guidance 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?

A specific verb-and-resource statement: it enumerates exactly what the tool surfaces (dependencies, dependents/mentions, complementary tools, reported integrations, each with a reason). It does not name any sibling (scbee_project_card, scbee_score, etc.) to sharpen the boundary, though the closing 'Not for websites' does mark a scope edge.

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?

Explicit when-to-use triggers: 'choosing what to pair or integrate with a project' and 'looking for related tools,' plus one negative scoping rule ('Not for websites'). It stops short of pointing to an alternative tool when the user actually wants scoring or a project card.

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.