Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Create a new epic

create_epic

Creates a new Epic in Targetprocess from a required title plus optional project, release, and HTML description details.

Instructions

Create a new Epic in Targetprocess.

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": {
      "title": "<title>"
    },
    "name": "create_epic"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesEpic title
projectIdNoOptional Project ID -- defaults to TP_PROJECT_ID from config
releaseIdNoOptional Release ID to link this epic to (e.g. 145200)
descriptionNoOptional epic description (when provided, format as HTML)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

C2.3/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 for a mutation tool, yet it discloses nothing: not required permissions, not whether the caller's default project context is used, not what validation or failure modes exist, and not what the response returns. The only behavioral hint (projectId defaulting to TP_PROJECT_ID) lives in the schema rather than the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short, front-loaded sentence with no wasted words, but that brevity reflects under-specification rather than disciplined editing. There is no structure to speak of — no sections, no caveats, nothing beyond the restated name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter write tool with no annotations and no output schema, the definition is materially incomplete. An agent learns nothing about failure behavior, ID prerequisites, or what a created Epic looks like, so it must rely entirely on field-level schema text and guesswork.

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 every parameter carries an inline description, including the projectId default and the HTML formatting requirement for description, so the schema does the explanatory work. The description itself adds no parameter meaning, which is acceptable at this coverage level but not additive.

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

Purpose2/5

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

The sentence 'Create a new Epic in Targetprocess' restates the tool name (create_epic) and title ('Create a new epic') almost verbatim, adding only the product name. It conveys a verb and a resource but gives no scope or distinction from siblings such as create_feature, create_user_story, or create_bug, which share the identical 'create an entity' pattern.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from this text whether create_epic is the right choice versus create_feature when modeling work items, or what relationship an Epic has to those entities.

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