Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitProvider-getAll

Read-onlyIdempotent

Retrieves all configured Git provider integrations from a Dokploy instance so you can review available source-control connections.

Instructions

GET /gitProvider.getAll

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": "gitProvider-getAll"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety and idempotency are covered structurally. The description adds nothing beyond that: no note on whether secrets/private keys are included in the payload, no ordering, no pagination, and no scope (organization vs global).

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 a single route string with no filler, but brevity here is under-specification rather than conciseness. A raw HTTP path is not front-loaded prose an agent can reason over.

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 tool that returns all configured git provider integrations — potentially including sensitive credential metadata — the definition says nothing about the return shape, count, pagination, or visibility scope. With no output schema, the description is the only source of that information and it supplies none.

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 schema has zero properties and 100% coverage, so there are no parameter semantics to explain. Per the baseline for parameterless tools, a 4 applies; the description neither helps nor hurts here.

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?

"GET /gitProvider.getAll" merely restates the tool name and HTTP route; it conveys only that git providers are returned in bulk. It gives no indication of what a git provider record contains or how this differs from siblings such as gitProvider-allForPermissions.

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 at all — no mention of when to prefer this over gitProvider-allForPermissions, gitProvider-remove, or the other provider listing tools. The only implicit signal is "getAll", which the agent must interpret on its own.

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