Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get epic content

get_epic_content

Retrieve a Targetprocess Epic by ID to view its description, current state, and progress. Use it to inspect epic details before planning or updating related work.

Instructions

Get a Targetprocess Epic by ID, including its 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_epic_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEpic ID (e.g. 148813)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It indicates a read ('Get') and lists some returned fields, but it does not disclose permissions, error behavior when an ID is missing, idempotency, or rate limits.

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?

One sentence, front-loaded with the action and resource, and no unnecessary wording. It is appropriately sized for a simple lookup.

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 low-complexity lookup with full schema coverage, the description states the main returned fields and enough to call it. However, with no output schema and no annotations, it could say more about the return shape and failure behavior.

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 coverage is 100% and the single ID parameter is fully described in the schema, including length bounds and an example. The description's 'by ID' adds no syntax or semantic detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Get'), a specific resource ('Targetprocess Epic'), and a selection key ('by ID'), plus the fields returned. This clearly separates it from sibling content getters for bugs/features/user stories and from create_epic/update_epic mutations.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling alternative is referenced. The only implied usage is that a caller supplies an epic ID.

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