Skip to main content
Glama

Enable/disable a deployed endpoint

toggle_endpoint
Destructive

Flip a deployed endpoint between enabled and disabled while keeping its configuration. Use it to stop serving live traffic and restore it later; requires confirm=true to apply.

Instructions

Flips a deployed endpoint's enabled/disabled state (list_endpoints shows the current isEnabled). A disabled endpoint stops serving live traffic but keeps its configuration, so toggling it back on restores it. Powerful: requires confirm=true — first call WITHOUT confirm to preview, then again with confirm:true.

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": {
      "endpointId": "<endpointId>"
    },
    "name": "toggle_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to toggle. Omit/false returns a preview only.
endpointIdYesThe endpoint's id — from list_endpoints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond destructiveHint=true, the description discloses that live traffic stops, that configuration is retained and restoration is possible, and that a confirm flag is required with a preview-first workflow. It does not cover permission/auth requirements, but the safety-relevant behavior is well explained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the effect, then the consequence, then the required calling procedure. Nothing is redundant or buried.

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

Completeness4/5

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

For a two-parameter state toggle with no output schema and a single annotation, the description covers effect, side effects, reversibility, and the confirmation workflow. Only the shape of the preview response is left unspecified, which is minor.

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

Parameters3/5

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

Schema coverage is 100%: confirm's preview semantics and endpointId's origin from list_endpoints are already documented in the input schema. The description adds no parameter detail beyond that, so the baseline applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+effect: flipping a deployed endpoint's enabled/disabled state, and clarifies how the current state is observed via list_endpoints. It is clearly distinguishable from siblings like update_endpoint or delete_endpoint because it changes only the serving state.

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

Usage Guidelines4/5

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

Explains the operative context — a disabled endpoint stops live traffic but keeps configuration, so it can be restored — which implicitly frames it against deletion. It also prescribes the exact two-step invocation (preview first, then confirm:true), though it does not explicitly name a sibling alternative for the case where the user wants to remove the endpoint.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.