Skip to main content
Glama
mfa-servicenow-mcp

mfa-servicenow-mcp

by jshsakura

manage_workflow

Export legacy ServiceNow workflow graphs, list workflows, and retrieve version-specific activities to inspect and validate editor edits.

Instructions

LEGACY Workflow engine ONLY (wf_workflow/wf_activity); export writes a version's full graph to disk; verify checks edits applied in the editor. Flow Designer -> manage_flow_designer.

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": {
      "action": "<action>"
    },
    "name": "manage_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
limitNo
queryNoAdditional query string
tableNo
actionYes
activeNo
offsetNo
count_onlyNo
version_idNoSpecific version for activities
workflow_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.25.19
    • addedInput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / table
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changedv1.25.8
    • addedInput schema / properties / query / description
      Added value: +"Additional query string"
  3. Changed2 schema fields changedv1.24.83
    • removedInput schema / properties / confirm
      Removed value: -{
      -  "enum": [
      -    "approve"
      -  ],
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "action",
      -  "confirm"
      -]New value: +[
      +  "action"
      +]
  4. Addedv1.21.21
  5. Removedv1.21.13
  6. First observedv1.18.41

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It hints at side effects ('export writes a version's full graph to disk') and verification semantics, but those actions are not invocable per the enum, and there is no description of permissions, pagination behavior, or what 'list' and 'get_activities' return.

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

Conciseness3/5

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

It is short and front-loads the legacy scope, but the telegraphic style (semicolon fragments, '->' arrows) and references to unavailable actions make it cryptic rather than efficient. Brevity here costs clarity rather than removing waste.

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

Completeness2/5

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

For a 10-parameter tool with no annotations and no output schema, this description leaves far too much unexplained: action semantics, filtering parameters, pagination, and return shape are all absent. The export/verify content it does include cannot be acted on given the enum.

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

Parameters2/5

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

Ten parameters with only 20% schema description coverage, and the description explains almost none of them. It never mentions workflow_id, table, query, active, count_only, limit, or offset, and the only implicit reference to version_id is tied to a non-existent 'export' action.

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

Purpose3/5

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

It establishes scope ('LEGACY Workflow engine ONLY (wf_workflow/wf_activity)') and names the sibling that covers the modern path, so an agent can place it in the toolset. But the operations it actually describes (export, verify) are not among the schema's allowed actions ('list', 'get_activities'), so the stated purpose does not match what the tool can be asked to do.

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?

Explicit routing guidance is present: legacy engine only, and 'Flow Designer -> manage_flow_designer' names the alternative and the condition that selects it. What is missing is guidance on choosing between the tool's own actions, since only 'list' and 'get_activities' exist in the schema.

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