Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get feature comments

get_feature_comments

Retrieve comments for a Targetprocess feature using its ID, with an optional result limit. Use it to review feature discussion and feedback.

Instructions

Get comments for a TP feature by its ID

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>"
    },
    "name": "get_feature_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTP feature ID (e.g. 145636)
resultsNoNumber of comments to return, default is 25

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.1/5.0
Behavior2/5

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

Since no annotations are provided, the description bears the full behavioral burden. It is extremely brief and fails to disclose important operational traits like rate limits, authentication requirements, or the nature of the 'TP' prefix beyond what is assumed.

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?

The description is perfectly concise and direct. It uses only the necessary words to define the tool's primary function without any filler or fluff.

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 definition is adequate for a simple lookup function where the input is strictly defined by the schema. However, it is insufficient for a complex system as it lacks crucial operational behavioral context.

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?

Given that the schema coverage is 100%, the baseline for parameter semantics is a 3. The description adds minimal value by clarifying that the 'id' must be a 'TP feature ID,' which is mostly redundant given the schema's context.

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 clearly states the verb (Get), the resource (comments), and the object (TP feature ID). It is clear and specific, though it doesn't explicitly distinguish the function from other comment retrieval tools like 'get_bug_comments.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The definition provides no guidance on when to use this tool versus others. There are no prerequisites, contexts, or warnings about potential alternatives, forcing the agent to rely solely on sibling names for differentiation.

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