Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get process workflows

get_process_workflows

Retrieve all workflows for a specific Targetprocess process by providing its process ID, so you can inspect stages and workflow structure.

Instructions

Get all Targetprocess process workflows

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": {
      "processId": "<processId>"
    },
    "name": "get_process_workflows"
  }
}

Input Schema

NameRequiredDescriptionDefault
processIdYesProcess ID (e.g. 145636)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing. 'Get' implies a read, but there is no statement about read-only safety, whether results are paginated, whether inactive workflows are included, or what the response shape is.

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

Conciseness4/5

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

A single short sentence with zero filler and the resource front and center. It is efficient, though its terseness is partly the cause of the missing behavioral detail.

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?

The tool is simple (one required, fully documented parameter, no output schema), so the description is minimally adequate. It still omits what the returned workflows contain and how a process-level workflow list relates to the entity-specific workflow tools, which an agent would need to choose confidently.

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 processId is already documented in the schema with an example. The description adds no syntax, format, or scoping meaning beyond that, so the baseline 3 applies.

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 (Get) and resource (Targetprocess process workflows), so an agent knows it retrieves workflow definitions scoped to a process. It does not, however, explicitly differentiate itself from near-neighbors like get_bug_workflows or get_user_story_workflows, leaving the agent to infer that this one is process-level rather than entity-level.

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

Usage Guidelines2/5

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

No when-to-use guidance and no mention of alternatives or prerequisites. The 'all' wording hints at an unfiltered list, but the description never says when to prefer this over the sibling workflow getters or what a process must exist first.

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