Skip to main content
Glama

toggle_trigger

Enable or disable a trigger without deleting its configuration; omit enabled to toggle the current state, then verify the returned is_active value after concurrent calls.

Instructions

Enable or disable a trigger without deleting its configuration. Set enabled for the desired state; omitting it toggles the current state. Concurrent calls can race, so verify the returned is_active value.

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": {
      "trigger_id": "<trigger_id>",
      "enabled": "<enabled>"
    },
    "name": "toggle_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue enables the trigger; false disables it
trigger_idYesTrigger UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.4
    • changedInput schema / properties / enabled / description
      Previous value: -"true para habilitar, false para desabilitar"New value: +"true enables the trigger; false disables it"
    • changedInput schema / properties / trigger_id / description
      Previous value: -"UUID do trigger"New value: +"Trigger UUID"
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false; the description goes beyond them by warning that concurrent calls can race and by telling the agent to verify the returned is_active value, plus noting the configuration is preserved. That is real behavioral context the annotations do not carry. The only blemish is the 'omitting it toggles the current state' clause, which conflicts with the required 'enabled' parameter and adds ambiguity to an otherwise solid disclosure.

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 short sentences, front-loaded with the scope constraint and followed by the parameter rule and the concurrency caveat. No filler and nothing 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 tool with full schema coverage and annotations covering the safety profile, the description covers the essentials: scope, state semantics, race behavior, and a return-value cue (is_active) despite there being no output schema. It falls short only because the omit-to-toggle claim is unreconciled with the required parameter.

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 description coverage is 100%, so both parameters are already documented, making 3 the baseline. The description does try to add meaning for 'enabled' (desired-state semantics, omit-to-toggle fallback), but that addition contradicts the schema's required list, so it detracts rather than clarifies.

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?

The description names a specific verb pair (enable/disable) and resource (trigger), and immediately bounds the scope with 'without deleting its configuration' — which cleanly separates it from delete_trigger and update_trigger among the siblings. An agent can identify the operation without opening the schema.

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

Usage Guidelines3/5

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

It implies the tool is the right choice for state changes that should preserve configuration, which is a useful contrast to delete_trigger, but it never states when to prefer update_trigger or test_trigger instead. Usage guidance is implied rather than explicit.

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