Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get TP feature content

get_feature_content

Retrieves a Targetprocess Feature by ID, returning its description, state, and progress for status checks and reporting.

Instructions

Get a Targetprocess Feature by ID, including description, state, and progress

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

Input Schema

NameRequiredDescriptionDefault
idYesTP feature ID (e.g. 145636)

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?

No annotations are supplied, so the description carries the full burden. It discloses that the response includes description, state, and progress, which is useful transparency about return shape, but says nothing about permissions, not-found/error behavior, or whether the payload is trimmed versus the full entity.

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?

One front-loaded sentence with no filler; the resource and identifying mechanism come first and the returned-field list comes second. It is efficient, if slightly thin for a tool with no output schema.

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 simple single-argument read tool this is close to sufficient, and listing returned fields compensates partially for the absent output schema. However, without annotations the description should at least confirm this is a read-only, non-mutating operation and note behavior on an invalid or missing ID.

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?

There is a single required parameter with 100% schema coverage, including a format example, so the schema already does the work. The description adds only 'by ID', which restates the schema rather than adding new meaning.

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 and resource ('Get a Targetprocess Feature by ID') and enumerates the fields returned, which separates it from the bug, epic, and user-story content siblings. It is clear on its own, though the sibling differentiation is carried by the word 'Feature' rather than stated explicitly.

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?

'By ID' implies the tool is used when a Feature ID is already known, but there is no statement of when to prefer it over search_tp_cards for discovery or over the feature sub-resource tools (comments, user stories). Usage is only inferable from the phrasing, not stated.

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