Skip to main content
Glama

set_workflow_enabled

Turn one of the coach's workflows on or off (confirm-gated). Turning one on needs Coach Pro or a gym plan.

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": {
      "workflowId": "<workflowId>",
      "enabled": "<enabled>"
    },
    "name": "set_workflow_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
enabledYes
workflowIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write-but-not-destructive profile, so the description's added value is the 'confirm-gated' two-step contract and the plan entitlement requirement — both are behavioral facts not present in annotations. It stops short of saying what the preview returns or whether the call is idempotent, but the important surprises are disclosed.

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?

Two short sentences, front-loaded with the action, no filler or redundant restatement of the tool name. The parenthetical is the only compression device and it carries real meaning.

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

Completeness3/5

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

For a 3-parameter mutation with no output schema, the description covers the confirm gate and the entitlement prerequisite, which is the right core. It omits error behavior for an invalid or inaccessible workflowId and does not describe what the preview payload contains, both of which matter for a gated toggle.

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 only 33% — confirm is documented, enabled and workflowId are not. The description partially compensates by mapping 'on or off' to the enabled boolean and 'confirm-gated' to the confirm flag, but it never says where a workflowId comes from or what a valid one looks like, leaving real ambiguity.

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

Purpose4/5

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

States a specific verb and resource: toggling one of the coach's workflows on or off. That is clearly distinguishable from create/delete/update workflow siblings. It does not, however, explicitly differentiate itself from set_gym_workflow_enabled, which an agent would likely confuse with it based on names alone.

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?

The description gives a real precondition for the enable direction ('needs Coach Pro or a gym plan'), which is genuinely useful routing information. It does not say when to prefer this over the gym-workflow toggle sibling, nor what to do if the entitlement check fails, so usage is only partially covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.