Keelen

List GitHub Repositories

list_github_repos

List repos the workspace's GitHub connection can see (for import_project).

Each entry has full_name, default_branch, private, language, pushed_at. A
`full_name` is what import_project(repo_full_name) connects. Reading the
list can MINT a short-lived GitHub installation token, so this is not a pure
read. Returns 409 if GitHub isn't connected yet — connect_github() is
required first. A provider failure is translated into a typed, actionable
error instead of passing GitHub's response through: a missing or suspended
App installation, a revoked OAuth token, or a non-rate-limit permission
denial is a 409 naming connect_github(); a recognized rate limit is a 429;
other provider failures are a 502; a timeout or transport failure is a 503.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Discloses a non-obvious side effect the annotations only partly imply: reading the list can mint a short-lived installation token, so it is not a pure read. This is consistent with readOnlyHint=false and adds real context. It then gives a complete, typed error taxonomy (409/429/502/503) mapping each provider failure to a named cause, which is far beyond what annotations provide.

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 purpose, then entries, then side effect, then error behavior — a logical progression with no filler. It runs a bit long in the error enumeration, but every clause carries distinct information rather than repeating structured fields.

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?

Complete for a zero-parameter, side-effecting list call: scope, downstream consumer, token-minting behavior, connection precondition, and a full failure taxonomy are all covered. An output schema exists, so the description is not obliged to detail return values, yet its field list is a useful pointer.

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?

The tool takes zero parameters, so the baseline is 4. The description goes further by explaining the return fields (full_name, default_branch, private, language, pushed_at) and clarifying that full_name is the value import_project consumes, which adds semantics not present in the empty input schema.

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 (List) and resource (GitHub repos) plus the exact scope: repos the workspace's GitHub connection can see. It also names the consuming sibling, import_project, so an agent can immediately distinguish this from connect_github or import_project.

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 ties the tool to import_project (for import_project) and states the precondition that connect_github() must run first, backed by the concrete consequence (409 if GitHub isn't connected). This is exactly the when-to-use / prerequisite guidance the dimension asks for.

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

All Keelen 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.