Skip to main content
Glama
Sign In
Muninn

Muninn

by kamysh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

search_knowledge

Performs hybrid semantic and full-text search across curated notes for an exact repository path key, helping AI coding agents retrieve relevant shared knowledge.

Instructions

Hybrid semantic + fulltext search over curated notes under an exact repository-path key; no worktree/family resolution. Use the established main-checkout key for shared notes.

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>",
      "repo": "<repo>"
    },
    "name": "search_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesExact repository-path key, usually the main checkout path for shared notes; no worktree/family resolution.
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a real behavioral trait — no worktree/family resolution, so the key must match exactly — but omits ranking behavior, result limits/pagination, and any permission or rate-limit 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?

Two dense sentences with the search-mode-and-scope constraint front-loaded; every clause carries information. Minor redundancy in restating the no-worktree-resolution rule that also appears in the repo schema description.

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

Completeness4/5

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

Complete for a hybrid search over a knowledge base: the key behavioral constraint (exact repo key, no resolution) and the recommended key choice are stated. Return format and ranking needn't be explained since there is no output schema, though limit/pagination semantics remain unaddressed.

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 coverage is only 33% (only 'repo' documented), so the description must compensate. It adds meaningful semantics for 'repo' (exact key, no worktree/family resolution, main-checkout for shared notes), but says nothing about 'query' syntax or the 'limit' parameter's meaning or default.

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?

States a specific verb and resource: 'Hybrid semantic + fulltext search over curated notes'. The scope ('curated notes under an exact repository-path key') distinguishes it from the generic search_hybrid/search_fulltext/search_semantic siblings by data domain, though it never names an alternative outright.

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?

Usage is implied by the 'curated notes' domain and the directive 'Use the established main-checkout key for shared notes', which tells the agent which key to supply. However, it gives no explicit when-to-use-this-vs-search_hybrid guidance or exclusions, leaving the sibling choice to inference.

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