OrionBI

List GitHub repositories

github_list_repositories

Read-only

List repositories you can access with a GitHub connection (your own or one shared with you). Returns up to 50 repositories ordered by most recently updated. To list an organization's repositories instead, pass its login — the name in its URL, not its display name.

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

Input Schema

Name	Required	Description	Default
`org`	No	Optional. List this organization's repositories instead of your own. Must be the org's LOGIN exactly as it appears in its URL (github.com/<login>) — not its display name, and not the connection's name.
`connection`	No	Which 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.

First observedNov 4, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavior: a hard cap of 50 results and ordering by most recently updated, which tells the agent when the listing is truncated. It stops short of saying whether pagination or further pages exist, which is the one behavior an agent still has to guess.

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, front-loaded with what the tool returns, then the org override. No filler; every sentence carries either scope, return shape, or a parameter caveat.

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

Completeness5/5

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

With only two optional parameters, no output schema, and annotations handling safety, the description covers what an agent still needs: the result count limit, sort order, and how to switch to org scope. Nothing material is missing for calling it correctly.

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 both parameters are already documented, including the login-vs-display-name distinction for 'org' and the connection-label caveat. The description reinforces the org login rule but adds no new syntax, format, or default behavior beyond the schema, so baseline 3 applies.

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 and resource ('List repositories') plus the exact scope: repositories reachable through a GitHub connection, whether owned or shared. It also carves out the org variant, so an agent can distinguish this from github_search_repositories or github_list_connections without opening any schema.

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?

Gives clear when-to guidance for the two modes: call with no arguments for your accessible repos, or pass 'org' to target an organization's repos. It does not explicitly name alternatives (e.g. use github_search_repositories when you have a name filter), so routing among siblings is only implied.

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

All OrionBI tools Inspect

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

Need Help?