Skip to main content
Glama
Sign In
coolify-mcp

coolify-mcp

by frndchagas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List GitHub App repositories

getGithubAppRepositories
Read-only

List all repositories a GitHub App can access by providing its app ID. Use this to identify available repos for deployment and management.

Instructions

List repositories accessible to a GitHub App.

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": {
      "github_app_id": "<github_app_id>"
    },
    "name": "getGithubAppRepositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
github_app_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already indicates a safe read operation. The description adds the scope that repositories are 'accessible to a GitHub App', which clarifies the subset returned. However, it does not disclose additional behavioral traits such as pagination, authentication needs, or what 'accessible' means in practice.

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?

The description is a single front-loaded sentence with no redundant words. The verb 'List' is present at the start and every word contributes meaning.

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?

For a simple read-only list tool with one parameter and existing annotations, the description covers the essential purpose. It does not explain the return format, but given the absence of an output schema and the obvious nature of the result (a list of repositories), the description is adequate.

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 0%, but the single parameter (github_app_id) is self-explanatory and the description links it to the GitHub App. The description does not explicitly state where the ID comes from or its format beyond the schema's integer type, but the naming and context make the meaning reasonably clear.

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?

The description uses the specific verb 'List' and identifies the resource as 'repositories accessible to a GitHub App', which clearly distinguishes it from sibling tools like getGithubAppBranches (branches) and listGithubApps (the apps themselves).

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?

The description implies when to use (when you need repositories for a GitHub App) but provides no explicit guidance on when not to use, nor does it reference alternatives. It does not mention exclusions or comparisons with sibling tools.

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