Skip to main content
Glama
Sign In

OrionBI

by ai.orionbi
OverviewDiscussionsAdmin

List GitHub connections

github_list_connections
Read-only

List the GitHub connections you can use — both your own and any shared with you, with granted scopes and whether each is shared (read-only) or owned. Tokens are never returned. Each row carries TWO different identifiers, and they are not interchangeable: name is this connection's local label, and is what you pass as connection to the other tools; login is the GitHub account it is authenticated as, and is what GitHub resolves — use it for org, and for the owner half of owner/repo. They are the same string for most accounts, which is exactly why it matters when they are not.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: "Tokens are never returned" is a concrete data-exposure guarantee, and it discloses the visibility model (own + shared, shared ones are read-only).

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?

Front-loaded with what the tool does, then the identifier warning. Dense but every sentence carries information; the closing clause "which is exactly why it matters when they are not" is mildly rhetorical but reinforces a real failure mode.

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 carries the return-shape burden and does so: each row has scopes, shared/owned flag, `name` and `login`. It omits ordering, pagination, and what happens with zero connections, which are minor for a small list tool.

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

Parameters5/5

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

There are zero input parameters, so the baseline is 4; the description earns the extra point by explaining the semantics of the returned identifiers and mapping `name` directly onto the `connection` parameter of sibling tools. That resolves the single highest-risk caller error for this tool family.

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?

Opens with a specific verb and resource ("List the GitHub connections you can use") and immediately scopes it: own plus shared, with granted scopes and shared/owned status. An agent knows exactly what comes back 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?

Implies the primary use case by stating that `name` is "what you pass as `connection` to the other tools," which tells an agent to call this first when it needs a connection identifier. It stops short of an explicit when-not or a named alternative (e.g. versus postgres_list_connections).

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