Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Delete a relation between two cards

delete_card_relation

Removes a relation between two Targetprocess cards using the relation's own ID, not the card IDs. Retrieve the relationId from get_card_relations before deleting.

Instructions

Delete (remove) a relation between two TP cards by the relation's own ID — not the card IDs. To find the relationId, call "get_card_relations" for one of the cards; each entry includes a "relationId" field.

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": {
      "relationId": "<relationId>"
    },
    "name": "delete_card_relation"
  }
}

Input Schema

NameRequiredDescriptionDefault
relationIdYesThe relation ID to delete (the "relationId" field from "get_card_relations", e.g. 20748)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A4/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 behavioral burden. It usefully discloses the main failure mode (confusing relationId with card IDs) and how to look the ID up, but says nothing about irreversibility, required permissions, or what the call returns on success or failure — gaps that matter for a destructive operation.

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?

Two short sentences, front-loaded with the destructive action and the ID scoping rule, then the recovery step. Every clause earns its place with no boilerplate.

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 one-parameter delete tool with no output schema, the definition covers what the agent most needs: which identifier to use and where to find it. Only confirmation of irreversibility and error behavior are missing.

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 parameter is documented in the schema with an example value, so the baseline applies. The description reinforces the relationId-vs-card-ID distinction but adds no format or validation detail beyond what the schema already states.

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 ("Delete (remove) a relation between two TP cards") and explicitly scopes it to the relation's own ID rather than the card IDs. This distinguishes it cleanly from the sibling delete_card and from get_card_relations/create_card_relation.

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 actionable prerequisite guidance: to obtain the relationId, call "get_card_relations" for one of the cards and read the relationId field. It does not state when not to use it or what happens if the relation does not exist, but the usage context is clear enough for an agent to act.

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