Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get User Story workflows

get_user_story_workflows

Fetch all Targetprocess user story workflows with sub-states to identify available story statuses and support workflow-aware automation.

Instructions

Get all Targetprocess user story workflows, with sub-states

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_user_story_workflows"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that results are unfiltered ('all') and include sub-states, which is genuine behavioral context, but it says nothing about read-only safety, permissions, ordering, or the shape of a workflow record.

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?

A single front-loaded sentence with zero filler. The scope qualifier 'all' and the content qualifier 'with sub-states' both earn their place.

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 zero-argument tool this is nearly sufficient, but there is no output schema, so the description is the only source of return-value information — and 'with sub-states' only hints at the record structure without describing fields, nesting, or ordering.

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?

The tool takes zero parameters, so there is no parameter semantic burden on the description. Baseline 4 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 and resource: 'Get all Targetprocess user story workflows, with sub-states.' The resource scope (user story workflows) inherently separates it from get_bug_workflows and get_process_workflows, but the description never names those siblings or says why to pick this one.

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?

Usage is implied by the name and the zero-argument read shape — an agent knows this fetches the workflow catalog. There is no explicit when-to-use or when-to-use-something-else guidance, and no mention of how it relates to get_bug_workflows or get_process_workflows.

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