Skip to main content
Glama

search_projects

Read-only

Search GitHub and GitLab for open source repositories by query, language, or stars. Returns installable project IDs with stars, language, and license details.

Instructions

Search GitHub and GitLab for open source repositories. Returns ids that install_project accepts, with stars, language and license.

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": {
      "query": "<query>"
    },
    "name": "search_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
forgeNoWhere to search (default all).
limitNoMaximum results (default 10, max 50).
queryYesSearch terms. GitHub qualifiers such as topic:cli or stars:>500 are allowed.
languageNoRestrict to a programming language, e.g. Rust.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds value beyond that by disclosing the return payload (ids, stars, language, license) and the downstream compatibility with install_project. It omits rate-limit or auth considerations for the external forges, which would be relevant for an open-world tool.

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 tight sentences: the first establishes what is searched, the second establishes what comes back and what it is good for. No filler, and the action is front-loaded.

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 compensates by naming the returned fields and their downstream use. For a four-parameter, fully-documented read-only search this is near complete; only multi-forge behavior nuances (pagination, rate limits) 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%, so all four parameters including the forge enum, limit bounds and GitHub qualifier syntax are already documented in the schema. The description adds only the general open-source scope, not parameter-level detail, so baseline 3 applies.

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?

States a specific verb and resource ('Search GitHub and GitLab for open source repositories') and clarifies the query scope is public open-source repos rather than installed ones. It stops short of naming list_projects as the contrasting sibling, but the install_project hand-off still differentiates it from the project-management siblings.

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?

'Returns ids that install_project accepts' establishes the workflow context clearly: search first, then install. There are no explicit exclusions (e.g., when to use list_projects instead of searching), which keeps it below a 5.

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