Skip to main content
Glama
Sign In
BitPull

BitPull

by SamuealPK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_repos

Read-only

Search shared BitPull code and public GitHub repositories by keyword before writing from scratch, returning repository IDs, summaries, and host availability.

Instructions

Search code shared by other BitPull users, and public GitHub repositories BitPull offers (source: github), before writing it from scratch. Returns repo ids, summaries and whether a host is online.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesKeywords, e.g. 'jwt refresh express'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover read-only and open-world behavior, so the bar is lower. The description does add useful disclosure of result shape (repo ids, summaries, host-online status) and the two corpora searched, but says nothing about authentication, rate limits, ranking, or pagination against the limit cap.

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?

A single front-loaded sentence with no filler. The parenthetical "(source: github)" and the dangling "BitPull offers" clause are slightly garbled but cost little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter search with no output schema, the description decently covers result fields and source pools. It still leaves the agent guessing about the limit parameter, result ordering, and whether the search is federated across both corpora or selectable.

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

Parameters2/5

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

Schema coverage is 50%: query is documented as free-text keywords, but limit is undocumented in both schema and description. The description adds no parameter meaning at all, not even confirming that "search terms" map to the query field or how multiple repositories are ranked and capped.

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?

"Search code shared by other BitPull users, and public GitHub repositories" is a specific verb+resource with an explicit scope (two source pools) and a stated intent ("before writing it from scratch"). It is clearly a code-search tool, though it never contrasts itself with the similarly named bitpull_search_hub sibling.

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?

The phrase "before writing it from scratch" gives a concrete moment to reach for this tool, which is real when-to-use guidance. There are no exclusions, no mention of when a hub or web search would be preferable, and the (source: github) hint is left unexplained.

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