Skip to main content
Glama
Sign In

OrionBI

by ai.orionbi
OverviewDiscussionsAdmin

Search GitHub repositories

github_search_repositories
Read-only

Search repositories across GitHub using a GitHub connection (your own or one shared with you). Accepts a GitHub search query (supports qualifiers like language:, user:, org:, stars:). Returns up to 30 matches ordered by best match.

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

Input Schema

NameRequiredDescriptionDefault
sortNoOptional sort field (default best match).
orderNoSort order when sort is set (default desc).
queryYesGitHub repository search query, e.g. "topic:cli language:go stars:>100".
connectionNoWhich GitHub connection to use, by its name from github_list_connections. This is a local label for the connection, NOT a GitHub username — for anything GitHub has to resolve, use that connection's login instead. Optional when you have exactly one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint false), so the description's job is to add context — and it does, disclosing the 30-result cap and best-match default ordering, both material to how an agent interprets results. It omits auth/permission requirements and rate-limit behavior, keeping it short of a 5.

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 sentences, both front-loaded with the most decision-relevant facts (what it searches, what query syntax it accepts, how many results come back). No filler, no restatement of the title.

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 correctly supplies the result-count limit and default ordering, which is the key return-shape information an agent needs. Given the simple 4-parameter read-only tool, this is nearly complete; only permission/rate-limit context is missing.

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 description coverage is 100%, so all four parameters are already documented, and the schema even carries a query example and enum explanations. The description adds a bit of meaning by enumerating additional qualifiers (language:, user:, org:, stars:) and clarifying the connection can be shared, but this is largely reinforcing rather than extending the schema — baseline 3.

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?

The description gives a specific verb and resource ("Search repositories across GitHub") and names the input format (a GitHub search query with qualifiers), so the agent knows exactly what the tool does. It does not explicitly distinguish itself from the sibling github_list_repositories, leaving the search-vs-list choice to inference.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the mention of qualifiers like language:/user:/org:/stars: signals this is for filtered/discovery queries, and "your own or one shared with you" hints at the connection prerequisite. There is no explicit when-to-use or when-not-to-use guidance versus github_list_repositories or github_search_code.

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

All OrionBI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources