Skip to main content
Glama

Find unambiguous Git abbreviations

bpj_release_git_hash_prefix
Read-onlyIdempotent

Find a unique short prefix for each supplied full Git object ID within that input set.

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": {
      "hashes": "<hashes>",
      "minimum": "<minimum>"
    },
    "name": "bpj_release_git_hash_prefix"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashesYes
minimumYes

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, closed-world, so safety needs no restating. The description adds one genuinely useful trait beyond them: uniqueness is computed relative to the supplied set rather than the whole repository. It does not say what is returned when two IDs share a long common prefix, nor how the minimum interacts with forced collisions.

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 with no filler, and the scoping qualifier is placed where it matters. It is arguably too tight for a tool whose input format and return shape are both undefined.

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?

No output schema exists, so the description should describe what comes back (a mapping of ID to prefix, a list, a length?), and it does not. Combined with the unexplained 'minimum' parameter and the unstated encoding of the hashes string, an agent would have to guess at both ends of the call.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries full burden. It clarifies that hashes are full object IDs and that there are several of them, but the schema types hashes as a single bounded string with no stated delimiter or format, and 'minimum' is never explained despite being required. Only one of two parameters gets any real clarification.

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?

Names a specific verb and resource: find a unique short prefix for each full Git object ID. The phrase 'within that input set' adds real scope information, distinguishing this from git's own global abbreviation. It stops short of naming any sibling, but the operation is distinct enough to be recognizable on its own.

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 by the operation itself; there is no statement of when to reach for this versus another release helper, no mention of prerequisites, and no note on what to do when uniqueness is impossible. The 'within that input set' clause does implicitly tell the agent that results are batch-relative, which is the only contextual guidance present.

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.