Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get commit message for a task or bug

get_commit_message

Generate a formatted commit message for a task or bug ID, including feature, user story, and title details to keep commits consistent.

Instructions

Returns the formatted commit message string for a given task or bug ID. Formats:

  • Task on a user story: "F# US# T# "

  • Bug on a user story: "F# US# B# "

  • Standalone bug (no user story): "B# "

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

Input Schema

NameRequiredDescriptionDefault
idYesThe task or bug ID (e.g. 145789)
typeYesWhether the ID refers to a task or a bug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the exact shape of the return value for three distinct cases (task on user story, bug on user story, standalone bug). It omits failure behavior — e.g. what happens if the ID doesn't match the supplied type or has no parent user story.

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?

One front-loaded summary sentence followed by a compact bulleted list of output templates; every line adds information and nothing is padded.

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

Completeness4/5

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

For a two-parameter read tool with no output schema, explaining the returned string format is exactly the right content, and the three-case enumeration covers the main variability. Only the error/edge-case behavior is left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both `id` and `type` are already documented, but the format bullets add real meaning: they show that `type` selects the 'T#' versus 'B#' prefix and that user-story membership changes the output template. That is useful semantics beyond the enum's plain wording.

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 and resource — 'Returns the formatted commit message string' — scoped to 'a given task or bug ID'. This is clearly distinct from sibling readers like get_bug_content or get_task_content, which return record data rather than a generated commit string.

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?

Usage is only implied: the tool's name and purpose make it obvious it is used to produce a commit message, but the description never says when to call it versus the many content-fetching siblings, nor any prerequisite such as knowing whether the ID is a task or bug. No exclusions or alternatives are named.

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