Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

List my user stories

list_my_user_stories

Retrieve User Stories assigned to you for an overview of current work, with optional filtering by state and pagination controls.

Instructions

List User Stories assigned to me. Use this to get an overview of current work. Optionally filter by state.

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": "list_my_user_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoPagination offset, default is 0
takeNoNumber of results to return, default is 25
stateNoFilter by state name (e.g. "Open", "In Progress", "Done")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. "List ... assigned to me" reasonably conveys a read-only, caller-scoped query, but it says nothing about result ordering, page size limits, or whether completed items are included by default, leaving the agent to infer behavior.

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?

Three short sentences with the core scope (assigned to me) front-loaded and no filler. The middle sentence about "overview of current work" is marginally informational but not wasteful.

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 simple three-parameter, all-optional read tool with a fully documented schema and no output schema, the definition covers the essentials. The only gap is that it does not mention pagination defaults or result ordering, which are minor for this tool's complexity.

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 skip, take, and state are already fully documented with defaults and an example. The description's "Optionally filter by state" only restates the schema, 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?

The description states a specific verb and resource ("List User Stories") plus a meaningful scope constraint ("assigned to me"), which distinguishes it from feature-scoped or release-scoped siblings. It does not name any sibling explicitly, so it stops short of a 5.

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?

"Use this to get an overview of current work" gives a generic hint about intent, but there is no guidance on when to prefer this over list_my_bugs, get_feature_user_stories, or other retrieval tools, and no exclusions or prerequisites are stated.

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