Skip to main content
Glama
MCP Dokploy Online
by igoruam

github-getGithubRepositories

Read-onlyIdempotent

Retrieve GitHub repositories for a specified GitHub connection ID, enabling users to inspect available repositories for deployment or infrastructure management.

Instructions

GET /github.getGithubRepositories

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": {
      "githubId": "<githubId>"
    },
    "name": "github-getGithubRepositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
githubIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 profile is covered externally. The description adds nothing beyond that — no note on pagination, auth requirements, or what happens with an unknown githubId — and an open-world remote call deserves at least a hint about failure modes or result shape.

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 this is under-specification rather than conciseness: one bare endpoint line with no front-loaded explanation of what is returned or required. Brevity here costs the agent necessary context.

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

Completeness2/5

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

With no output schema, one undocumented required parameter, and an open-world remote call, the description should carry substantial weight but instead carries none. An agent cannot tell what the response looks like or how to construct a valid githubId.

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% and there is one required parameter, githubId, whose meaning (account id vs. username vs. connection id) the description never clarifies. The single sentence contains no parameter information at all, leaving the agent to guess the identifier format.

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 a raw route string, 'GET /github.getGithubRepositories', which essentially restates the tool name. It implies fetching repositories for a GitHub account, but offers no scope, no filtering behavior, and no differentiation from siblings such as gitlab-getGitlabRepositories or bitbucket-getBitbucketRepositories.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, when not to, or which sibling to prefer for a different provider or for branch-level data. The agent must infer everything from the tool name alone.

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