Skip to main content
Glama

krusch_git_search_symbols

Read-onlyIdempotent

Search a codebase for functions, classes, methods, exports, and markdown sections by query and optional symbol type, so you can locate definitions without manual browsing.

Instructions

Locate functions, classes, methods, exports, and markdown sections across the codebase.

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_git_search_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNo
queryYes
symbol_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. Beyond that, the description adds nothing: no result-count limits, no ranking/ordering of matches, no indication of whether the whole repo or a single ref is scanned. The list of symbol kinds is essentially a restatement of purpose rather than behavioral 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?

A single well-formed sentence with the verb and scope front-loaded and no filler. It is efficient, though efficiency here comes partly from omitting necessary detail rather than from tight editing of rich content.

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?

Three parameters at 0% coverage, no output schema, and an undefined `symbol_type` domain mean an agent has to guess at invocation shape. For a search tool whose whole value depends on how query and filters combine, the description is too thin to call it correctly on first attempt.

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 three parameters, so the description carries the full burden and fails it. It never explains that `query` is a name/text pattern, what `repo` scopes to, or what values `symbol_type` accepts (no enum is defined either), leaving the most important filtering parameter undocumented anywhere.

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 ("Locate") plus the resource kinds it matches (functions, classes, methods, exports, markdown sections) and implies repo-wide scope with "across the codebase", which differentiates it in spirit from a per-file sibling like file_symbols. It stops short of naming any sibling, so the distinction is inferred rather than stated.

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 explicit when-to-use, when-not-to-use, or named alternative. An agent cannot tell from this text whether to reach for this tool or krusch_git_file_symbols / krusch_git_semantic_search, and the fact that symbol search takes a free-text query vs. a file path is left to be discovered from the schema.

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