Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get release bugs

get_release_bugs

Retrieves bugs associated with a specified Targetprocess release, optionally including descriptions and limiting results for release quality tracking.

Instructions

Get release bugs

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure and delivers none: no statement on what subset of bugs is returned, whether results are filtered by status, ordering, truncation by the results cap, or required permissions.

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

Conciseness2/5

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

Three words carried over from the title, so there is no wasted wording in a literal sense, but the brevity comes from under-specification rather than efficiency. Nothing is front-loaded because there is no substantive content to order.

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

Completeness1/5

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

For a 3-parameter, 2-required tool with no annotations and no output schema, the definition omits everything an agent needs: what the return shape is, what the withDescription flag actually expands, and how the results cap affects completeness. It is completely inadequate for the tool's complexity.

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, and the baseline of 3 applies. The description adds no meaning beyond that, and notably does not clarify the schema's internal inconsistency where the results parameter defaults to 300 but its own text says the default is 100.

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?

Tautological: description restates name/title.

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

Usage Guidelines1/5

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

The description contains no when-to-use guidance, no exclusions, and no mention of any alternative tool. An agent must guess whether to prefer this or get_release_open_bugs / get_user_story_bugs / list_my_bugs for a given question.

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