Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-toggleRequests

Idempotent

Enable or disable request handling for a Dokploy instance by setting the requests toggle to true or false.

Instructions

POST /settings.toggleRequests

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": {
      "enable": "<enable>"
    },
    "name": "settings-toggleRequests"
  }
}

Input Schema

NameRequiredDescriptionDefault
enableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations declare openWorldHint=true and idempotentHint=true but do not declare destructive or readOnly behavior, so the description must carry the burden of explaining what state changes. It adds nothing: no statement of what gets enabled/disabled, whether the change is reversible, what permissions are required, or what happens on repeated calls beyond the idempotency hint.

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 text is a single route string with no wasted words, but it is under-specified rather than concise. A bare endpoint path front-loads nothing an agent can act on.

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 state-mutating toggle with no output schema and no annotation coverage of destructive/readOnly behavior, the definition is completely inadequate. Nothing describes the effect of the call, the meaning of the boolean, or how to verify the result.

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

Parameters2/5

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

Schema description coverage is 0% with one required boolean parameter 'enable', and the description provides no meaning at all for it. The agent must guess whether 'enable' accepts new requests versus merely enabling the settings panel, which is a material ambiguity for a toggle operation.

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 HTTP route 'POST /settings.toggleRequests', which essentially restates the tool name with no added explanation. It names a resource ('requests') and an implied toggle action, but never says what 'requests' are or what toggling them does, so an agent cannot distinguish this from siblings like settings-haveActivateRequests or settings-toggleDashboard on purpose alone.

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 when-to-use, when-not-to-use, or alternative guidance of any kind. Nothing tells the agent under what circumstances toggling requests is appropriate versus checking their state with settings-haveActivateRequests.

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