Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get assignment roles

get_assignment_roles

Fetch all available assignment roles with their IDs so you can select valid Targetprocess roles such as Business Analyst or Developer.

Instructions

Returns all available assignment roles (e.g. Business Analyst, Developer) with their IDs.

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_assignment_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. "Returns all available" implies a safe, read-only, non-filtered enumeration and it discloses the payload shape (roles plus their IDs), but it says nothing about ordering, stability, or whether the list is cached/static.

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?

A single front-loaded sentence with no filler; the parenthetical examples of role names genuinely clarify the domain vocabulary rather than padding the text.

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 zero-parameter reference lookup with no output schema, the description says enough: what is returned, that IDs are included, and what the values look like. Only minor gaps remain, such as ordering or whether the set can change.

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 no parameter meaning to convey; the baseline for a no-arg tool applies. The description correctly signals that the call needs no input to enumerate every role.

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?

"Returns all available assignment roles ... with their IDs" states a specific verb (returns), resource (assignment roles), and scope (all available), plus concrete example values. It is clearly a distinct lookup tool rather than a mutator, though it does not explicitly contrast itself with any 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: an agent can infer this is the reference lookup to call when it needs a role ID before assigning work. There is no statement of when to call it versus other get_* tools or any prerequisite context.

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