Skip to main content
Glama

Use template in workflow step

spur_set_workflow_step_template
Idempotent

Set which saved template a workflow's send step uses (send_email ← email template, send_sms ← SMS template, send_direct_mail ← postcard/letter template). Get step_ids from spur_get_workflow. If the workflow is active, enrolled owners get the new template from their next send.

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": {
      "workflow_id": "<workflow_id>",
      "step_id": "<step_id>",
      "template_id": "<template_id>"
    },
    "name": "spur_set_workflow_step_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoRequired when editing a live workflow
step_idYesstep_id from spur_get_workflow
template_idYesTemplate id (UUID from a Spur list/search tool)
workflow_idYesWorkflow id (UUID from a Spur list/search tool)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
      +  "const": true,
      +  "description": "Required when editing a live workflow",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, closed-world mutation. The description adds genuinely useful behavior beyond them: that on an active workflow, enrolled owners receive the new template from their next send — a downstream effect an agent should know before swapping a live step's template.

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 sentences, front-loaded with the action and its type mapping, then the prerequisite and the live-workflow consequence. No redundant restatement of the name or title.

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 mutation tool with full annotation and schema coverage and no output schema, the definition supplies the missing pieces: type pairing rules, the step_id source, and the live-workflow propagation effect. It leaves unstated what happens on a template/step type mismatch (error vs. rejection), a minor gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining the semantic relationship between step type and acceptable template type, which prevents pairing an SMS template with a send_email step. It still doesn't explain the confirm parameter's role, but the schema does that explicitly.

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 and resource ('Set which saved template a workflow's send step uses') and immediately disambiguates with a mapping of step kinds to template kinds (send_email ← email template, send_sms ← SMS template, send_direct_mail ← postcard/letter). An agent can distinguish this from template-creation and workflow-editing siblings without inspecting schemas.

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?

Gives the key prerequisite explicitly: 'Get step_ids from spur_get_workflow', routing the agent to a sibling before calling this. It also states the condition under which the change propagates (workflow active → next send), but does not say when to prefer other tools or what to do if the step is not a send step.

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.

Resources