Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Create a relation between two cards

create_card_relation

Link two Targetprocess cards by creating a master-slave relation with a named relation type, such as “Depends on,” to model dependencies between user stories, bugs, or features.

Instructions

Create a relation between two TP cards (UserStory, Bug, Feature, etc.). The Master is the source of the relation and the Slave is the target — e.g. for a "Depends on" relation, the Slave depends on the Master (Master must be done first). NOTE: relationType is matched by name against this instance's relation types. If unsure of the exact name, call "get_relation_types" first. The handler resolves the name to its ID before creating the relation.

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": {
      "masterId": "<masterId>",
      "slaveId": "<slaveId>"
    },
    "name": "create_card_relation"
  }
}

Input Schema

NameRequiredDescriptionDefault
slaveIdYesSlave card ID — the target of the relation (e.g. 145790)
masterIdYesMaster card ID — the source of the relation (e.g. 145789)
relationTypeNoRelation type name as defined in this instance (e.g. "Depends on", "Relate to"). Resolve exact names via "get_relation_types". Defaults to "Depends on".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A4.1/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 full burden. It does disclose useful internals — that relationType is matched by name and resolved to an ID by the handler, and that it defaults to 'Depends on' — but says nothing about permissions required, duplicate-relation behavior, or what happens when an unknown name is passed. That leaves meaningful behavioral gaps for a mutation 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?

Front-loaded with the core action, then the direction clarification, then the NOTE on relation-type resolution. Every sentence contributes, though the direction point is stated twice (once abstractly, once via the 'Depends on' example) and could be tightened.

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 3-parameter mutation tool with no output schema, the description covers the action, parameter meaning, and the main failure mode (wrong relation-type name). It does not describe the return value or duplicate/error behavior, but nothing critical to invoking it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: it explains the directionality in operational terms ('the Slave depends on the Master — Master must be done first') and the name-to-ID resolution for relationType. This goes past restating field definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a relation between two TP cards') and immediately clarifies the master/slave direction semantics, which is the one thing that distinguishes this from a generic link operation. An agent can tell this apart from delete_card_relation and get_card_relations by name alone.

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

Usage Guidelines4/5

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

Gives explicit pre-call guidance: call get_relation_types first if the relationType name is uncertain, and explains the direction convention with a concrete 'Depends on' example. It does not explicitly state when not to use it (e.g. when a relation already exists), but the usage context is clear.

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