Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get TP user story content

get_user_story_content

Fetches a Targetprocess user story's content by ID, letting AI assistants retrieve story details for review or analysis.

Instructions

Get tp card (user story) content by specified id, e.g. 145789

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": {
      "id": "<id>"
    },
    "name": "get_user_story_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTP (or tp) ID (e.g. 145789)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.1/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 burden of behavioral disclosure. Beyond the verb 'Get' implying a read, it says nothing about what the returned content contains, whether it includes description/acceptance criteria, auth requirements, or behavior when the ID does not exist or the user lacks access.

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?

One short sentence with the action and key front-loaded; the 'e.g. 145789' illustration earns its place by showing the format. Nothing is padded, though the example is duplicated from the schema rather than contributing new information.

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 simple one-parameter read tool the shape is nearly adequate, but with no output schema and no annotations the description is the only place to learn what 'content' means and none of that is stated. An agent cannot anticipate the return payload or error behavior before invoking.

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 coverage is 100% and the single 'id' parameter already documents its type, 5-9 length constraint and format. The description's example '145789' merely echoes the schema's own example, adding no new constraint or interpretation beyond structured data.

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+resource: 'Get tp card (user story) content by specified id'. The parenthetical maps internal jargon 'tp card' to 'user story', and pairing it with the id-keyed retrieval distinguishes it from the bug/epic content siblings by name. It stops short of naming which sibling to use when the id is unknown.

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?

The phrase 'by specified id' implies the caller must already hold a TP ID, which is the only usage precondition conveyed. There is no explicit when-to-use, no mention that search_tp_cards is needed first when the ID is unknown, and no exclusions versus the other get_user_story_* siblings.

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