Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get release features

get_release_features

Retrieve features assigned to a Targetprocess release by providing the release name and optional result limit.

Instructions

Get release features

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>"
    },
    "name": "get_release_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRelease name
resultsNoNumber of results to return, default is 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about whether the call is read-only, how results are ordered or paginated, or what happens when 'results' exceeds available items. The schema's internal inconsistency (default 50 versus 'default is 100') is left unclarified.

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?

The single phrase is technically brief but represents under-specification rather than conciseness, since it conveys no information beyond the tool name. There is no front-loaded detail because there is no detail at all.

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?

With no annotations and no output schema, the description is the only channel for behavioral and return-value context, and it supplies none. An agent cannot tell what shape the features come back in or how many to expect.

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 both parameters are documented in the schema itself, which sets the baseline at 3. The description adds no meaning about the release-name format or how the results limit interacts with pagination.

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 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 mention of alternatives, and no stated prerequisites such as whether a release must exist or be current. The agent must infer the use case entirely from the name.

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