Skip to main content
Glama
cq27-dev

rag-rat

by cq27-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

rationale_search

Search cached review and issue rationale by keyword; each hit includes the thread's distilled root cause, decision, and outcome.

Instructions

Search cached tracker rationale snippets (review comments, issue / change-request discussion) by keyword. A hit whose thread has a distilled decision record carries it as record (the model's root-cause / decision / outcome over the whole thread).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
includeNoWhat to include: `fallback` (off by default). Without it, a query naming a tracker item answers with that item's literal references alone whenever any exist.
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. Changed8 schema fields changedv0.23.2
    • removedInput schema / $defs / McpGraphMode
      Removed value: -{
-  "enum": [
-    "none",
-    "compact",
-    "full"
-  ],
-  "type": "string"
-}
    • addedInput schema / $defs / RationaleInclude
      Added value: +{
+  "description": "`rationale_search` `include` flags. `fallback` off by default.",
+  "enum": [
+    "fallback"
+  ],
+  "type": "string"
+}
    • removedInput schema / $defs / SearchInclude
      Removed value: -{
-  "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"
-}
    • changedInput schema / properties / include / description
      Previous value: -"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."New value: +"What to include: `fallback` (off by default). Without it, a query naming a tracker item\nanswers with that item's literal references alone whenever any exist."
    • changedInput schema / properties / include / items / $ref
      Previous value: -"#/$defs/SearchInclude"New value: +"#/$defs/RationaleInclude"
    • 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 carries the full burden. It mentions that 'fallback' is off by default and that without it, a query returns literal references if any exist, which provides some behavioral detail. However, there is no disclosure of potential side effects (it is read-only, a safe assumption but not stated), rate limits, or how the 'record' field is populated. The worktree behavior (silently ignored) is in the schema but not in the description, though it is a useful behavioral trait.

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 sentence, front-loading the core action and resource. It avoids unnecessary fluff and includes a valuable detail about the 'record' field. It is well-structured and easy to read, though it could benefit from a second sentence on when to use it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters, a moderate schema coverage of 50%, and no output schema, the description is somewhat thin. It does not explain the return structure beyond the 'record' attribute, nor does it mention pagination or how results are ordered. It also does not clarify the difference between this tool and semantic_search, which is a critical gap for an agent to select it correctly. The description is adequate for a basic understanding but lacks enough detail for confident invocation in all cases.

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?

The schema description coverage is 50%, meaning half the parameters are undocumented in the schema. The description adds some value by explaining the 'record' field but does not clarify the purpose of 'query' beyond 'keyword' (which is somewhat redundant) nor how 'limit' behaves (e.g., does it cap results or snippets?). The 'include' parameter is only partially explained in the schema and not at all in the description. Given the moderate coverage gap, the description should compensate more but does not.

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 that the tool searches cached tracker rationale snippets by keyword, mentioning review comments and discussion. It includes a detail about distilled decision records, which helps distinguish it from a general search tool. However, it does not explicitly contrast with similar sibling tools like semantic_search, though the mention of 'keyword' and 'snippets' implies a lexical search.

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?

The description gives some context (searching by keyword, using a worktree to scope reads), but no explicit guidance on when to use this tool versus alternatives like semantic_search. It does not mention when not to use it, nor does it suggest alternatives for different needs (e.g., semantic search for related concepts rather than exact keywords). The 'fallback' include flag is mentioned only in the schema, not in the description.

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