Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Adds provided content to TP card (user story) as a comment

add_comment_with_user

Adds a comment to a specified Targetprocess card by ID and mentions a selected user, after retrieving users with get_users to identify the correct person.

Instructions

Adds provided content as a comment to the specified tp card by id, e.g. 145789 and mentions the user in the comment CRITICAL WORKFLOW: 1) call 'get_users' to get list of available users 2) find the user by email, first name, or last name in the users list

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": {
      "id": "<id>",
      "comment": "<comment>",
      "user": "<user>"
    },
    "name": "add_comment_with_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTP card id, usually user story or bug ID (e.g. 145789)
userYesUser to add to the comment, from "get_users" tool
commentYesComment content to add

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?

With no annotations supplied, the description carries the full behavioral burden. It discloses the meaningful side effect that the target user is mentioned/notified, but says nothing about required permissions, what happens if the user IsActive is false, whether the mention fails silently, whether content is plain text or markdown, or what the response returns. For a write operation with zero annotation coverage, this leaves substantial behavioral gaps.

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?

Front-loaded with the operation, followed by a clearly labeled CRITICAL WORKFLOW block. Two short numbered steps, no filler prose. The workflow is slightly incomplete in that it never states the final step of calling this tool with the found user, but overall the structure is efficient and scannable.

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?

The tool has a required nested user object and no output schema or annotations, so the description must justify how the object is populated, which it partly does via the get_users workflow. However it omits failure modes, permission requirements, and mention semantics for an inactive user. Adequate but not complete for a mutation tool with a nested required parameter.

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 the nested user object fields (Email, FirstName, LastName, IsActive) are each documented in the schema, so the baseline is 3. The description does reinforce that the user must be sourced from 'get_users' and echoes the id example format, but this largely restates what the schema already declares. It adds little syntax or validation meaning beyond the schema.

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?

States a specific verb and resource: adds provided content as a comment to a TP card identified by id, and adds a distinguishing detail that the user is mentioned in the comment. That mention detail is what separates it from the sibling 'add_comment', though the description never names that sibling explicitly. An agent can identify the operation but must infer the sibling boundary from the name alone.

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?

Provides a concrete prerequisite workflow: call 'get_users' first, then locate the user by email, first name, or last name before invoking this tool. That is useful invocation guidance, but there is no when-to-use versus when-not guidance and no mention of when to prefer 'add_comment' over this mention-capable variant. Guidance is procedural rather than selection-oriented.

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