Skip to main content
Glama
cq27-dev

rag-rat

by cq27-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

commits_touching_query

Discover commits tied to a query by combining message matches with file-change evidence, revealing what work relates to a topic.

Instructions

Combine commit-message matches with current file-change evidence for a query — "what work relates to X?" across both messages and the files that changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
worktreeNoAbsolute path of the checkout to scope reads to — pass a linked worktree to read its branch overlay. Defaults to the server's working directory. A path that is not a linked worktree of this repo is silently ignored: results then come from the indexed checkout, with no error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.23.2
    • removedInput schema / $defs
      Removed value: -{
-  "McpGraphMode": {
-    "enum": [
-      "none",
-      "compact",
-      "full"
-    ],
-    "type": "string"
-  },
-  "SearchInclude": {
-    "description": "`semantic_search` `include` flags. `git`/`papertrail` are on by default (omit `include` to keep\nthem); `generated`/`fallback` are off by default.",
-    "enum": [
-      "generated",
-      "git",
-      "papertrail",
-      "fallback"
-    ],
-    "type": "string"
-  }
-}
    • removedInput schema / properties / explain
      Removed value: -{
-  "default": false,
-  "type": "boolean"
-}
    • removedInput schema / properties / graph_limit
      Removed value: -{
-  "default": 3,
-  "format": "uint32",
-  "minimum": 0,
-  "type": "integer"
-}
    • removedInput schema / properties / include
      Removed value: -{
-  "default": null,
-  "description": "What to include: `git`, `papertrail` (both on by default), `generated`, `fallback` (off by\ndefault). Omit to keep defaults; an explicit list is the exact on-set.",
-  "items": {
-    "$ref": "#/$defs/SearchInclude"
-  },
-  "type": [
-    "array",
-    "null"
-  ]
-}
    • removedInput schema / properties / include_graph
      Removed value: -{
-  "$ref": "#/$defs/McpGraphMode",
-  "default": "compact"
-}
  2. Changed3 schema fields changedv0.23.0
    • removedInput schema / properties / worktree / default
      Removed value: -null
    • changedInput schema / properties / worktree / description
      Previous value: -"Absolute path to a linked git worktree you're working in. When set, results are served from\nthat worktree's branch overlay (its committed + uncommitted changes) on top of the indexed\ncheckout; omit to query the indexed checkout. An unrelated/invalid path falls back to it."New value: +"Absolute path of the checkout to scope reads to — pass a linked worktree to read its branch overlay. Defaults to the server's working directory. A path that is not a linked worktree of this repo is silently ignored: results then come from the indexed checkout, with no error."
    • changedInput schema / properties / worktree / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
  3. First observedv0.9.0-3b4b4b7

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions combining evidence but does not disclose whether the operation is read-only, any side effects, performance implications, or return format. For a query tool without annotations, this is a significant gap.

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?

The description is a single, clear sentence that front-loads the purpose. It is concise and avoids redundancy, though it could benefit from breaking out the two evidence types for clarity. Still, it is appropriately sized.

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?

Given the tool's complexity (combining two evidence types) and the lack of an output schema, the description is incomplete. It does not explain how results are formatted, how 'limit' affects output, or what 'file-change evidence' concretely means. An agent would need to infer too much.

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

Parameters1/5

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

Schema coverage is only 33% (only worktree has a description). The description adds no information about the 'query' or 'limit' parameters beyond the schema's minimal definitions. With low schema coverage, the description fails to compensate, leaving agents without a clear understanding of parameter semantics.

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 clearly states the tool's purpose: combining commit-message matches with file-change evidence for a query. It specifies the verb 'combine' and the resource 'commits', and distinguishes from pure message search by mentioning both dimensions. However, it does not explicitly name sibling tools, so it falls short of a 5.

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?

The usage is implied: use this when you need both commit messages and file-change evidence. There is no explicit guidance on when to prefer this over alternatives like commit_search or git_history_for_path, nor any exclusions or prerequisites. The description provides context but not explicit routing.

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