Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Set Business Value on a TP card

set_business_value

Set the Business Value (Priority) for a Targetprocess User Story, Feature, or Epic by resolving valid priority IDs with get_priorities first.

Instructions

Set the Business Value (Priority) on a Targetprocess User Story, Feature, or Epic. Business Value in the TP UI maps to the Priority field in the API. CRITICAL WORKFLOW: Call "get_priorities" first to retrieve the list of valid priority IDs and their names for this instance before calling this tool — do not guess priority IDs.

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>",
      "entityType": "<entityType>",
      "priorityId": "<priorityId>"
    },
    "name": "set_business_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID of the card to update (e.g. "151282")
entityTypeYesEntity type of the card
priorityIdYesPriority ID — resolve via "get_priorities" first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that this is a single-field mutation limited to three entity types and that IDs must be validated against the instance first, but it does not say whether an existing value is overwritten, what happens on an invalid ID, what permissions are required, or what the call returns.

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?

Three short lines, front-loaded with the action and target, then the naming clarification, then the critical prerequisite. Every sentence carries information an agent needs and nothing is repeated.

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 three-parameter mutation with full schema coverage, the description covers purpose, scope, and the priority-ID prerequisite. But with no annotations and no output schema, it leaves the mutation semantics (overwrite behavior, error conditions, return value) unstated, which an agent cannot infer from structured fields alone.

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%, so all three parameters are already documented in the schema, including the entityType enum and the note to resolve priorityId via get_priorities. The description adds the UI-to-API field mapping but no additional syntax, format, or validation detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb ("Set") and resource ("Business Value (Priority)") plus the exact scopes it applies to (User Story, Feature, Epic). It also resolves a naming ambiguity by stating that the TP UI "Business Value" corresponds to the API "Priority" field, so an agent knows precisely which field is being mutated.

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

Usage Guidelines4/5

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

Gives an explicit prerequisite workflow: call "get_priorities" first and do not guess priority IDs, which is the exact failure mode an agent would otherwise hit. However, it offers no when-not-to-use guidance and does not describe how this relates to other field-setting or card-update 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