Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get relation types

get_relation_types

Retrieves all Targetprocess relation types (ID and name) so you can identify the correct relationType value when creating card relations.

Instructions

Get all relation types available in this Targetprocess instance (id + name). Use this to find the correct relationType name for "create_card_relation".

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden; it discloses that results are instance-scoped reference data and that each entry is an id/name pair. That covers the essential behavioral profile of a 0-parameter read. Minor gaps remain: no statement about whether the list is static configuration versus user-specific, or about result size.

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 with zero filler: the first defines the resource and output, the second defines the use case. Purpose is front-loaded before the cross-reference, which is the right order.

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?

There is no output schema and no annotations, so the description must supply both the purpose and the return shape, and it does ('id + name'). For a trivial parameterless lookup this is nearly complete. It could add one clause on how the name is to be passed into create_card_relation, but nothing an agent needs to invoke it 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate, and the baseline applies. The mention of returned fields (id + name) usefully clarifies the shape of each element even though no input schema detail is needed.

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 ('Get all relation types'), scopes it ('available in this Targetprocess instance'), and even names the returned fields ('id + name'). This is distinguishable from sibling readers such as get_card_relations or get_card_current_status, which return entity data rather than a relation-type lookup table.

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?

Explicitly says when to use it: 'Use this to find the correct relationType name for create_card_relation.' That routes the agent to the right consumer of the output. It stops short of a 5 because it gives no when-not guidance (e.g., that it isn't needed if the relationType name is already known) and doesn't mention related lookup tools.

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