Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get features in an epic

get_epic_features

Retrieve all Features for a Targetprocess Epic using its Epic ID. Enables listing child features for planning or reporting.

Instructions

Get all Features belonging to a Targetprocess Epic.

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

Input Schema

NameRequiredDescriptionDefault
idYesEpic ID (e.g. 148813)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and delivers little. It does not indicate whether results are paginated, whether completed or closed Features are included, or whether full feature records or identifiers are returned — all material for a bulk read.

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 clean sentence with no wasted words, and the resource scope is front-loaded. It is efficient but borders on under-specification given what it omits.

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 one-parameter read tool with a fully documented schema, the definition covers the essential scope. It leaves gaps a caller would care about — result shape and pagination — but nothing that would cause the tool to be invoked with the wrong argument.

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 single id parameter is documented with an example format, so the schema does the heavy lifting. The description adds only that the id refers to an Epic, which is baseline reinforcement rather than 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?

States a specific verb ('Get') and resource ('all Features belonging to a Targetprocess Epic'), making the retrieval scope legible without opening the schema. It stops short of differentiating itself from related readers like get_epic_content or get_release_features, which the agent must infer from names alone.

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 description gives no explicit when-to-use guidance, no exclusions, and names no alternative. An agent must infer from the name that this is the epic-scoped feature listing versus feature content or release feature tools.

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