Skip to main content
Glama

Search Commits

search_commits
Read-onlyIdempotent

Search commit history by query to find relevant changes and filter results by scope, date, impact, or tech debt risk in project memory.

Instructions

Search commit history by query

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_commits"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch query to match in commit messages
scopeNoFilter commits by a specific scope
sortByNoSort commits by date or impact score
maxCountNoMaximum number of commits to return. Default: 50
use_test_dbNo
techDebtAuditNoFilter for high impact commits with low trust or missing validation

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
commitsNo
detailsNoAdditional error context
successYes
categoryNoError category (validation, query, connection, internal)
changelogNo
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv9.1.0
    • changedInput schema / properties / maxCount / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
    • removedInput schema / properties / sortBy / enum
      Removed value: -[
      -  "date",
      -  "impact"
      -]
  2. First observedv9.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that: it does not explain what the impact score means for sorting, how techDebtAudit selects commits, or what the result set looks like. With annotations doing all the work, this sentence contributes no additional behavioral context.

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 five-word sentence with zero filler and the core action front-loaded. It is efficient, though its brevity stems from under-specification rather than disciplined editing.

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?

For a six-parameter search tool with an output schema and multiple overlapping siblings, this is too thin. Concepts central to correct invocation, such as what a "scope" is and what "impact score" or "techDebtAudit" select, are never explained. An agent must infer all search semantics from field names.

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 83%, above the 80% threshold, so the schema already documents query, scope, sortBy, maxCount, and techDebtAudit. The description adds no meaning on top of that, and the undocumented use_test_db parameter is left unexplained in both places. Baseline 3 applies since the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Search commit history by query" names a specific verb and resource, so the basic action is unambiguous. However, it gives no differentiation from close siblings like get_commit_history, analyze_commit_patterns, or get_unreleased_commits, all of which operate on the same commit data. An agent cannot tell from this text alone which of those to pick.

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 guidance, and no named alternative. Given that commit history is reachable through several sibling tools, the absence of any routing signal is a real gap.

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