Skip to main content
Glama
MCP Dokploy Online
by igoruam

gitProvider-toggleShare

Idempotent

Enable or disable sharing a Git provider with the organization by specifying the provider ID and shared status.

Instructions

POST /gitProvider.toggleShare

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": {
      "gitProviderId": "<gitProviderId>",
      "sharedWithOrganization": "<sharedWithOrganization>"
    },
    "name": "gitProvider-toggleShare"
  }
}

Input Schema

NameRequiredDescriptionDefault
gitProviderIdYes
sharedWithOrganizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations declare openWorldHint and idempotentHint, but the description adds nothing beyond the raw route — it does not say what gets flipped, whether it affects only this provider, whether it requires admin rights, or what a toggle response looks like. The description carries no behavioral information at all.

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 shortness here is under-specification rather than conciseness — a bare HTTP verb plus path that leaves every question unanswered.

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?

A mutation tool with two required, undocumented parameters, no output schema, and only sparse annotations; the description supplies none of the missing context about effect, permissions, or return value.

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%, so the description must compensate, and it does not: gitProviderId and sharedWithOrganization are never explained in the text. The agent gets no hint about the toggle direction implied by passing a boolean.

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 only the endpoint string "POST /gitProvider.toggleShare", which restates the tool name rather than explaining what toggling share does (enable sharing with an organization? flip it on/off?). A reader must infer purpose entirely from the name; nothing distinguishes it from siblings like gitProvider-remove or application-saveGitProvider.

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 pick instead. No prerequisites, no mention of what sharing means versus connecting/saving a provider.

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