Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get card relations

get_card_relations

Retrieve all relations for a Targetprocess card by ID—dependencies, blockers, links, and duplicates—with direction showing whether each related card is master or slave.

Instructions

Get all relations (Dependency, Blocker, Relation, Link, Duplicate) for a TP card (UserStory, Bug, Feature, etc.) by its ID. Each relation shows the related card and the direction: - "outbound" — this card is the Master (e.g. for Dependency, the related card depends on this card) - "inbound" — this card is the Slave (e.g. for Dependency, this card depends on the related card)

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_card_relations"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTP card ID (e.g. 145789)

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?

No annotations are supplied, so the description carries the burden of disclosure. It does valuable work by explaining the return payload — each relation includes the related card plus a direction flag — and defines outbound=Master vs inbound=Slave with a Dependency example. It says nothing about permissions, pagination/limits, empty-result behavior, or whether deleted cards still appear, which are the remaining gaps for a zero-annotation tool.

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?

The primary purpose is front-loaded in the first line, with the direction semantics set off as a short bulleted gloss. Every sentence earns its place; the only quibble is the slightly verbose nested example explanation of Master/Slave.

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?

With no output schema, the description compensates by describing what each returned relation contains (related card + direction) and how to interpret direction. For a single-parameter read operation this is close to complete; only edge-case behavior (no relations, volume of results) is unaddressed.

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 is fully documented with type, length bounds and an example ('145789'). The description adds only the framing that ids refer to any TP card type (UserStory, Bug, Feature), which is mildly useful but largely duplicative — the baseline 3 is appropriate when the schema does the heavy lifting.

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 gives a specific verb and resource ('Get all relations ... for a TP card ... by its ID') and even enumerates the relation kinds (Dependency, Blocker, Relation, Link, Duplicate) and card types (UserStory, Bug, Feature). It stops short of naming which sibling to use instead, but the read-only retrieval purpose is unambiguous.

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 only implied: fetch a card's relations by ID. There is no explicit when-to-use/when-not guidance, no mention of how this relates to get_relation_types (the catalog of relation kinds) or to create_card_relation / delete_card_relation for mutations.

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