Skip to main content
Glama
Sign In
CONTRI

CONTRI

by alphasafal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Discover projects

discover_projects
Read-onlyIdempotent

Find active public GitHub projects by language or topic, ranked by recent human merges and open good-first-issues, to identify viable repositories for contribution.

Instructions

Active public projects ranked by recent human merges and open good-first-issues, by language or topic. 1 request per language signed in, ~7 anonymous.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discover_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoBypass the cache (costs requests)
queryNoTopic words, e.g. cli, accessibility
languageNoe.g. TypeScript, Python, Rust
personalizeNoMatch the signed-in user's languages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

The rate-limit disclosure ('1 request per language signed in, ~7 anonymous') is exactly the kind of operational context annotations cannot convey, and it is meaningful for an openWorldHint tool. It also implies the result set is a ranked list, though it does not say whether results are cached snapshots.

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 short sentences with zero filler: what it returns and how it is ranked come first, with the quota caveat second. Nothing could be removed without losing 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 at least pins down the sort order and the filter dimensions, and annotations cover the read-only/idempotent safety profile. A brief note on what a project record contains or the default page size would round it out, but an agent has enough to call it 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 coverage is 100%, so each parameter (query, language, personalize, force) is already documented, and the description mostly restates that filtering is by language or topic. The one added value is coupling the tool to a per-language request budget, which explains why 'force' is costly.

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?

Names the resource (public projects) and the ranking signal (recent human merges, open good-first-issues) plus the two filter axes, which is far more specific than the title. It only stops short of a 5 because it never explicitly contrasts itself with issue-oriented siblings like find_issues or repo_health.

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

Usage Guidelines2/5

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

There is no statement of when to reach for this versus the issue-finding or repo_health siblings, and no when-not guidance. The filter axes ('by language or topic') hint at usage, but selection is left entirely to inference.

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

Deploy Server

Other Tools