Skip to main content
Glama

Vercel OSS Registry

Search Vercel OSS projects

search_projects
Read-onlyIdempotent

Full-text search (fuzzy, prefix) over Vercel OSS Program projects by name, topics and description, with optional filters. Returns compact hits; call get_project for full details. Omit query to browse by filters.

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": "search_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoDefault: relevance with query, stars without
limitNo
queryNoKeywords, e.g. "animated react components" or "auth"
topicNoExact GitHub topic (see list_facets)
cohortNoe.g. "Spring 2026"
offsetNo
languageNoPrimary language, e.g. TypeScript
minStarsNo
includeUnavailableNoInclude repos that are gone or flagged

Output Schema

NameRequiredDescriptionDefault
hitsYes
totalYes
offsetYes
matchModeYes"or" means no project matched every term
nextOffsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description is free to add search semantics instead: matching is fuzzy and prefix-based, results are compact, and filters are optional since no parameter is required. It stops short of describing pagination behavior or result ordering when no sort is given, though the schema supplies the sort defaults.

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?

Three short sentences with no filler: search scope first, output shape and drill-down second, the no-query mode last. Every clause carries information an agent needs at call time.

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 an output schema present, the description needn't explain return fields, and it still flags that hits are compact. For a 9-parameter, no-required-parameter search tool it covers the essential decision points, with only minor gaps around pagination and how the filters combine.

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 67%, so most parameters are self-documenting. The description adds real meaning for query (it spans name, topics and description, not just text) and clarifies that omitting it switches the tool into browse mode, but it says nothing about language, minStars, cohort, topic, includeUnavailable or offset beyond what the schema already declares.

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 (full-text search, fuzzy and prefix) over a specific resource (Vercel OSS Program projects) and names the fields searched (name, topics, description). It also distinguishes itself from get_project, so an agent can tell which tool returns compact hits versus full records.

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 routing: 'call get_project for full details' for the drill-down case, and 'Omit query to browse by filters' for the no-keyword case. Both the primary and the alternative mode of invocation are stated rather than inferred.

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.