Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Assign a role to a user on a card

assign_role

Assigns a Targetprocess user to a specified role on one card, such as a User Story or Bug, using card, user, and role IDs.

Instructions

Assigns a user to a specific role on a single TP card (User Story, Bug, etc.).

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": {
      "cardId": "<cardId>",
      "userId": "<userId>",
      "roleId": "<roleId>"
    },
    "name": "assign_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYesTP card ID (e.g. 149350)
roleIdYesTP role ID — use get_assignment_roles to find the right ID
userIdYesTP user ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.2/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 behavioral burden, and it discloses nothing beyond the basic action. It does not state what happens if the role slot is already occupied (overwrite vs. error), what permissions are required, whether the assignment is reversible, or what the call returns. For a mutation tool with zero annotation coverage this is a meaningful gap.

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?

One front-loaded sentence with no filler, and the scope qualifier ('single TP card') is placed where it matters most. Nothing could be removed without losing meaning.

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?

The tool has three required parameters, no annotations, and no output schema, so the description is the only place behavioral context could live, and it does not supply it. It never addresses collision/overwrite semantics or failure modes, which matter for an assignment mutation.

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 description coverage is 100% and each of the three parameters is documented in-schema, including the pointer to get_assignment_roles for roleId. The description adds only the contextual framing that cardId refers to a single card, which is already implied by the schema wording; baseline 3 applies.

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 names a specific verb (Assigns) and resources (user, role, card) and scopes the operation to a 'single TP card (User Story, Bug, etc.)', which implicitly distinguishes it from the feature-level sibling assign_role_to_feature. It stops short of explicitly naming the alternative, so an agent must infer the card-vs-feature split from the wording.

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 by the purpose statement: an agent can infer 'call this when you need to give a user a role on a card', and the 'single TP card' phrasing hints at the boundary with feature-level assignment. There is no explicit when-to-use, no prerequisites, and no named alternative even though assign_role_to_feature exists as a close sibling.

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