Skip to main content
Glama

Workflow operations and diagnostics

spur_manage_workflow
Destructive

Read enrollments, execution logs or stats; duplicate as a draft; delete; unenroll one contact; retry failed enrollments. Retrying can resume real sends and requires approval.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds information annotations cannot express: retrying can resume real sends to real contacts and demands explicit approval. It does not explain what delete destroys (e.g. enrollments, logs) or whether unenroll is reversible, so a small gap remains.

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, no waste, with the action inventory front-loaded and the safety warning placed last for emphasis. Every clause maps to an actual action or a real risk.

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 composite multi-action tool with destructive branches and no output schema, the description covers the action set and the highest-risk behavior. It leaves lower-stakes return semantics (what stats or logs contain) unstated, which is acceptable given the complete schema but not fully exhaustive.

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% and the schema already documents confirm, so the baseline is met. The description still adds meaning by clarifying that duplicate produces a draft and that unenroll targets exactly one contact via enrollment_id, which the oneOf structure alone does not convey.

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?

The description enumerates concrete verb+resource pairs: read enrollments/logs/stats, duplicate as a draft, delete, unenroll one contact, retry failed enrollments. That is far more specific than the generic tool name or title, and it implicitly separates this sub-resource tool from config-oriented siblings like spur_get_workflow or spur_edit_workflow, though no sibling is named.

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 states one hard usage condition clearly: retrying requires approval. There is no guidance on when to pick this tool over spur_get_workflow or spur_enroll_owners_in_workflow, and no note that read actions are safe versus the destructive ones beyond the approval caveat.

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