Skip to main content
Glama
MCP Dokploy Online
by igoruam

github-getGithubBranches

Read-onlyIdempotent

Retrieve GitHub branches for a specified repository and owner to inspect available branches before deployment or configuration.

Instructions

GET /github.getGithubBranches

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": {
      "repo": "<repo>",
      "owner": "<owner>"
    },
    "name": "github-getGithubBranches"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYes
ownerYes
githubIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety and idempotency profile is covered structurally. The description adds nothing beyond that — no pagination behavior, no result cap, no error behavior for missing repos or unconfigured providers, which matters for an open-world remote call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity is under-specification rather than efficiency: a single endpoint path communicates no task-level information and is not front-loaded with intent. Nothing here earns its place as a description.

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

Completeness1/5

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

For a 3-parameter remote read with no output schema and no parameter documentation, the definition is essentially empty. An agent cannot determine which GitHub provider instance to use, what the response looks like, or whether results are paginated — all of which the description should have supplied given the schema and annotations say nothing about them.

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

Parameters1/5

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

Schema description coverage is 0% across 3 parameters, so the description carries the full burden — and it provides none. The meanings of 'owner', 'repo', and especially 'githubId' (provider instance vs. repository id) are left entirely ambiguous, making correct invocation a guess.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is the raw endpoint path "GET /github.getGithubBranches", which effectively restates the tool name rather than explaining in prose what it returns. It does not state that it lists branches for a given repository/owner, nor does it distinguish this from the GitLab/Bitbucket/Gitea siblings beyond the provider implied by the name itself.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (authenticated GitHub provider, existing repo), and no pointer to alternatives such as the gitea/gitlab/bitbucket branch tools. The agent must infer the entire usage context from the tool name.

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