Skip to main content
Glama

buygit_search

Search curated Git assets with license, supply-chain risk, and pricing. Filter by category, language, license, or stars; sort by relevance, newest, stars, or health.

Instructions

Search 78,094 curated, deduplicated, license-tagged Git assets — not raw GitHub search. Every result carries license + popularity + supply-chain risk + pricing in one shot. Filters: category slug, language, SPDX license, min stars. Sort: relevance | newest | stars | health. Prefer this when the user wants to use or buy a project, compare alternatives, or check license compatibility. Use github-mcp for private repos / Issues / commits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text query matched against title, short description, and tags.
categoryNoCategory slug from buygit_list_categories. Common: api-backends (20k), dev-tools (17k), wordpress-plugins (5.5k), ai-agents, saas-starters, boilerplates, ml-models, scripts.
languageNoPrimary language. Matched against Repository.language_summary (dominant language by bytes).
licenseNoSPDX license identifier. Exact match required.
min_starsNoLower bound on repo stars.
limitNoPage size (1-50).
cursorNoOpaque base64 cursor from a previous response.next_cursor for pagination.
sortNorelevance (default), newest, stars (desc), or health (last commit + activity).relevance

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of results in this page.
has_moreYesTrue when more results exist beyond this page; use next_cursor to fetch.
next_cursorNoOpaque cursor for the next page; null when has_more is false.
resultsYes
Behavior4/5

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

No annotations provided, so description fully discloses the tool's behavior: returns curated results with license, popularity, risk, and pricing. Read-only implied but not explicitly stated.

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 sentences plus a list, front-loaded with key differentiator, no wasted words.

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?

Given output schema exists, description still explains return fields and differentiates from siblings. Lacks mention of pagination, but schema covers cursor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with examples and descriptions. Description adds value by summarizing filters and explaining the context of results, enhancing parameter understanding.

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?

Description clearly states it searches curated Git assets, distinguishes from raw GitHub search, and lists key attributes like license, popularity, risk, and pricing.

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?

Explicitly states when to use (buy/use/compare/license check) and when not (private repos, Issues, commits) with reference to an alternative tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/genoxdeveloper/buygit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server