Skip to main content
Glama

Infer a release bump from commit subjects

bpj_release_commit_bump_signal
Read-onlyIdempotent

Choose a bump from subject-line breaking markers, features, fixes and performance changes.

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

Input Schema

NameRequiredDescriptionDefault
commitsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that breaking markers on subject lines drive the decision, but omits the output shape (no output schema exists) and does not say which marker syntax is recognized (e.g. '!' vs 'BREAKING CHANGE:') or how conflicting signals are prioritized.

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?

A single front-loaded sentence with no filler, and the decision inputs are listed up front. It is lean rather than padded, though the brevity leaves real gaps that a second sentence could have closed.

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, the description is the only place an agent can learn what is returned (a level? a string? a rationale?), and it does not say. For a domain-specific inference tool with a free-text input, the definition leaves the return value and marker syntax entirely unspecified.

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 0%, so the description must carry the parameter burden; it only implies the input is subject lines via 'subject-line'. The schema's title does say 'Commit subjects, one per line' with a 4000-char cap, but the description adds no guidance on line format, allowed prefixes, or what happens with malformed lines.

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 ('Choose a bump') and the exact input source ('subject-line breaking markers, features, fixes and performance changes'), so an agent knows this infers a semver level from commit text. It does not, however, differentiate itself from the sibling bpj_release_semver_bump, which plausibly does a similar bump decision from explicit change types.

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 when-not-to-use, and no named alternative. The description never says whether this should be preferred over bpj_release_semver_bump or bpj_release_conventional_changelog, so an agent must guess from names alone.

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.