callimachus

Overview Schema Source Related Servers Discussions Admin

search_current_project

Read-only

Search the current git repository's conversation history by keyword or optional hybrid semantic matching to answer project-specific questions.

Instructions

Keyword search scoped to the git repo this server runs in. Prefer it over search_threads for questions about the current project. One entry per thread; hybrid=true adds semantic matching.

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": {
      "query": "<query>"
    },
    "name": "search_current_project"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max threads (default 10, max 50).
`query`	Yes	The search query.
`hybrid`	No	Also match semantically (fuzzy or paraphrased queries; slower).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.11.4Nov 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "coverage": {
+          "properties": {
+            "blindSpots": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "lastIndexedAt": {
+              "type": [
+                "integer",
+                "null"
+              ]
+            },
+            "sources": {
+              "items": {
+                "properties": {
+                  "kind": {
+                    "type": "string"
+                  },
+                  "threads": {
+                    "type": "integer"
+                  }
+                },
+                "required": [
+                  "kind",
+                  "threads"
+                ],
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "required": [
+            "sources",
+            "lastIndexedAt",
+            "blindSpots"
+          ],
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "threads": {
+          "items": {
+            "properties": {
+              "projectPath": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "snippets": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "source": {
+                "type": "string"
+              },
+              "threadId": {
+                "type": "integer"
+              },
+              "title": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "ts": {
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "threadId",
+              "source",
+              "title",
+              "projectPath",
+              "ts",
+              "snippets"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "threads"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "notice": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "notice"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changed4 schema fields changedv0.11.3Nov 6, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / hybrid / description

Previous value: -"Fuse keyword + on-device semantic search."New value: +"Also match semantically (fuzzy or paraphrased queries; slower)."

changedInput schema / properties / limit / description

Previous value: -"Max results to return (default 20)."New value: +"Max threads (default 10, max 50)."

removedInput schema / title
```
Removed value: -"ProjectSearchArgs"
```

First observedv0.5.0Jun 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds useful behavior beyond that: results are scoped to the local git repo, granularity is one entry per thread, and hybrid adds semantic matching at a cost ("slower"). It does not discuss result cap behavior or ranking, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, with scope and the sibling routing stated first and the matching-mode note last. Every clause carries information an agent would act on; nothing is padding.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, and annotations cover safety and openness. Given a simple three-parameter read-only search, the description supplies everything else needed to call it correctly: scope, routing, and the effect of the only non-obvious parameter.

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 100%, so limit (default 10, max 50) and hybrid are already fully documented in the schema. The description's line about hybrid mostly restates the schema text, adding no new syntax or edge-case meaning; the 3 baseline is appropriate.

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 names a specific verb and resource ("Keyword search") plus an explicit scope ("scoped to the git repo this server runs in"), and it explicitly distinguishes itself from the sibling search_threads. An agent can tell which tool to pick without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Prefer it over search_threads for questions about the current project" names the alternative and the condition that selects it, which implicitly tells the agent to use search_threads for non-project questions. That is explicit routing guidance with no inference required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.