Skip to main content
Glama
cq27-dev

rag-rat

by cq27-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

papertrail_issue_search

Search cached tracker issues and change-requests by full text, retrieving distilled decision records and coalesced issue-PR pairs as unified results.

Instructions

Full-text search across cached tracker issue and change-request titles and bodies. A hit whose thread has a distilled decision record carries it as record (the model's root-cause / decision / outcome over the whole thread); coalesced issue↔PR pairs answer as one result.

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. Addedv0.18.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses search scope, the inclusion of distilled decision records as `record`, and the coalescing of issue↔PR pairs. It does not address staleness of the cache, auth, or ordering, but the provided behaviors are meaningful and non-obvious.

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 compact and front-loaded with the core action. The additional clauses about `record` and coalesced pairs earn their place, though the parenthetical explanation could arguably be trimmed. Overall, it is appropriately sized for the complexity.

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?

There is no output schema and no annotations, so the description must do more to explain return values and behavior. It covers two important output quirks but omits the general hit structure, pagination/ordering, and limitations of the cached index. Usable but not fully complete.

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 only 33%, so the description must compensate. It clarifies what `query` searches against (titles and bodies), but does not explain `limit` semantics or result shape. The compensation is partial, not complete.

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

Purpose5/5

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

The description specifies a clear verb and resource: full-text search over cached tracker issue and change-request titles and bodies. It also identifies what makes results distinct (distilled decision records, coalesced issue↔PR pairs), which differentiates it from sibling search tools.

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?

No guidance is given about when to use this tool versus alternatives such as semantic_search, commit_search, rationale_search, or papertrail_for_chunk/symbol/commit. The context is implied from the description but exclusions and selection criteria are absent.

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