Skip to main content
Glama
MCP Dokploy Online
by igoruam

github-githubProviders

Read-onlyIdempotent

Retrieves GitHub provider configurations from Dokploy so you can identify available integrations for repository access and deployment setup.

Instructions

GET /github.githubProviders

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 structurally. The description adds nothing beyond that — no note on whether this hits the live GitHub API (relevant given openWorldHint), no pagination, no auth or rate-limit context, and no statement of what is returned.

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?

The single route string wastes no words but conveys no structured information either; this is under-specification rather than conciseness. There is no front-loaded statement of intent an agent could act on.

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, the description is the only place to learn what a call returns (a list of GitHub provider entries, their fields, or an error shape), and it says none of that. For an openWorld read against an external service, this leaves the agent unable to predict the response.

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 no parameters (0 params, empty schema), so there is no parameter meaning for the description to carry; per the baseline for zero-parameter tools this scores well regardless of the terse text. No value is added, but none is needed.

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 bare HTTP route, 'GET /github.githubProviders', which merely restates the tool name and title rather than stating in prose what the tool does. An agent can infer a read of GitHub provider configuration, but there is no verb+resource explanation and no differentiation from siblings such as bitbucket-bitbucketProviders, gitea-giteaProviders, or gitlab-gitlabProviders.

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?

No when-to-use guidance is given: nothing indicates whether this lists configured providers, discovered providers, or connection status, and nothing distinguishes it from application-saveGithubProvider or the other provider-listing siblings. Any selection decision is left entirely to inference from the 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