Skip to main content
Glama

Group conventional changelog entries

bpj_release_conventional_changelog
Read-onlyIdempotent

Group Conventional Commit subjects by type and keep unmatched lines for manual review.

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": {
      "commits": "<commits>"
    },
    "name": "bpj_release_conventional_changelog"
  }
}

Input Schema

NameRequiredDescriptionDefault
commitsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one genuinely useful behavior beyond that — unmatched lines are preserved rather than dropped — but says nothing about which Conventional Commit types are recognized, ordering, or how the grouping is represented.

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

Conciseness4/5

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

One sentence, zero filler, with the primary action front-loaded ahead of the fallback behavior. Its brevity is close to under-specification for a tool with no output schema, which keeps it just below a 5.

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 output schema and 0% schema description coverage, the description carries the full burden of explaining the return value, yet it never shows what a grouped result looks like, which types become keys, or how unmatched lines appear. For a transformation tool whose entire value is its output shape, this leaves a significant gap.

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?

There is a single required parameter, and the schema title already says 'Commit subjects, one per line'. The description adds the meaningful constraint that the subjects must be in Conventional Commit form, which tells the agent the expected line syntax, but the 4000-character cap and what happens to malformed lines at input are not mentioned.

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?

The description gives a specific verb ('Group') and resource ('Conventional Commit subjects') plus the grouping key ('by type') and a secondary behavior for unmatched input. It is immediately clear what the tool produces, though it does not name or differentiate itself against any sibling tool.

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: you supply commit subjects, one per line, and get them bucketed. There is no statement of when to prefer this over the sibling semver-bump or commit-bump-signal tools, and no prerequisites or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.