Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Assign a role to a user on all user stories in a feature

assign_role_to_feature

Assign a user to a specific role across every user story in a Targetprocess feature by providing feature, user, and role IDs.

Instructions

Assigns a user to a specific role on every user story within a given feature.

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

Input Schema

NameRequiredDescriptionDefault
roleIdYesTP role ID — use get_assignment_roles to find the right ID
userIdYesTP user ID
featureIdYesTP feature ID (e.g. 149341)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the important behavioral trait that the assignment fans out to all user stories in the feature, which is real value. However, it omits overwrite semantics (what happens to an existing assignee in that role), idempotency, required permissions, and the response — significant gaps for an unannotated bulk mutation.

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?

A single front-loaded sentence with no wasted clauses; the scope qualifier lands early. It is efficient, though the brevity comes at the cost of the behavioral detail noted above.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-required-parameter bulk mutation with no annotations and no output schema, the definition covers the operation's shape but leaves out whether existing assignments are replaced, whether the call is safe to repeat, and what is returned. Adequate to start, not complete enough to call confidently.

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 parameter is documented in-schema, including a pointer from roleId to get_assignment_roles. The description only restates the parameter roles in prose and adds no format, constraint, or edge-case detail beyond the schema, so the baseline of 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 gives a specific verb ('Assigns'), the resources (user, role, user stories) and the scope ('every user story within a given feature'). An agent can distinguish this bulk-style assignment from a single-target operation, though it doesn't explicitly name the narrower sibling.

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 phrase 'on every user story within a given feature' — the agent can infer this is the bulk variant, but there is no explicit when-to-use, when-not-to-use, or named alternative such as a single-story role assignment. Nothing tells the agent what to do when only one story needs the role.

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