Skip to main content
Glama

krusch_fs_search

Read-onlyIdempotent

Search structural file pages and anchored PageMemory notes by query, category, and result limit to retrieve relevant workspace context for coding tasks.

Instructions

Search structural file pages and anchored PageMemory 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>"
    },
    "name": "krusch_fs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
categoryNoall
limit_tokensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that: it does not say what is indexed, how matches are ranked or whether they are fuzzy/literal, what 'anchored' means operationally, or what the caller gets back. For a search tool with a fully annotated safe profile, this is a missed opportunity rather than a contradiction.

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

Conciseness3/5

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

A single short sentence with no padding and the core intent front-loaded, so nothing is wasted. But for a four-parameter search tool with zero schema documentation, one sentence is undersized rather than concise; brevity here comes at the cost of missing semantics.

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?

With no output schema, no annotation-independent behavior text, and 0% parameter documentation, the definition leaves the agent without enough to invoke confidently: result format, ranking behavior, and the meaning of 'category' and token limits are all absent. Only the annotated safety profile is reliably communicated.

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?

Schema description coverage is 0% across four parameters, so the description must carry the load and does not: it never mentions the required 'query', the 'limit' default of 10, the 'limit_tokens' budget, or the 'category' filter whose default is 'all' but whose accepted values are unknown. An agent cannot tell whether 'category' selects page type, PageMemory type, or file category, which is a meaningful invocation risk.

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

Purpose3/5

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

States a verb ("Search") and two resource types ("structural file pages" and "anchored PageMemory notes"), so the general intent is recoverable. However, both resource terms are domain jargon that an agent unfamiliar with this system cannot resolve, and the description never distinguishes the tool from plausible siblings such as krusch_fs_locate, krusch_fs_read_page, krusch_git_search_symbols, or search_drive_rag.

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?

There is no when-to-use guidance at all: no statement of the conditions under which page/PageMemory search is preferred over file locating, page reading, git symbol search, or RAG search. No exclusions or prerequisites are given, leaving the agent to guess among many overlapping retrieval siblings.

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