Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get release active bugs

get_release_open_bugs

Retrieve active bugs for a Targetprocess release, excluding closed, done, passed, and ready-to-deploy items. Use it to track unresolved release issues.

Instructions

Get release active bugs (bugs that are not closed, done, passed, ready to deploy)

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": {
      "name": "<name>",
      "withDescription": "<withDescription>"
    },
    "name": "get_release_open_bugs"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRelease name
resultsNoNumber of results to return, default is 50
withDescriptionYesInclude description in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the real filtering semantics that define the result set. It does not say whether the filter is applied server-side, whether the response is ordered or paginated, or that this is a read-only call — and it is silent on the conflicting 'results' default (schema property default 200 vs. schema text 'default is 50').

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?

A single front-loaded sentence with the resource first and the disambiguating definition immediately after in parentheses. No filler, no restatement of the title, nothing that could be cut without losing meaning.

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 read with no output schema and no annotations, the definition covers what the tool returns in kind and which bugs qualify. It stops short of stating the release-name requirement explicitly, the ordering/scope of results, or resolving the contradictory default noted in the schema, so it is adequate but not complete.

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 (name, results, withDescription) are already documented in the schema. The description adds no additional meaning about release-name format, result caps, or what 'withDescription' costs in payload size; baseline 3 applies when the schema does the work.

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 and resource (get release active bugs) and operationalizes the ambiguous word 'active' with an explicit status exclusion list. The gap is sibling differentiation: it never says how it differs from the closely named get_release_bugs, so an agent must guess whether that sibling returns all bugs including closed ones.

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?

The parenthetical status definition implicitly tells the agent when this tool is the right choice (you want bugs still in flight, not closed/done/passed/ready-to-deploy ones). However, there is no explicit when-not guidance and no named alternative such as get_release_bugs for the all-status case, so routing between the two is left to inference.

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