Skip to main content
Glama

krusch_git_semantic_search

Read-onlyIdempotent

Search code symbols and snippets with keyword plus structural token ranking to find relevant repository matches.

Instructions

Search symbols and code snippets using keyword + structural token ranking.

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

Input Schema

NameRequiredDescriptionDefault
repoNo
limitNo
queryYes
limit_tokensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds only the ranking behavior (keyword plus structural tokens); it says nothing about result volume, ordering guarantees, or what repository scope is searched by default.

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 front-loaded sentence with no filler or redundancy. It is efficient, though the brevity reflects under-specification rather than density of useful information.

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 four undocumented parameters, no output schema, and no explanation of result shape, defaults, or repository scoping, the definition leaves too much unknown for a tool of this complexity. The annotations cover safety but not the operational behavior an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, and the description mentions none of them. It never explains what 'repo' scopes, what 'limit_tokens' constrains relative to 'limit', or that 'query' is a keyword expression, so an agent must guess at every argument.

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?

Names a specific verb (Search), the resources (symbols and code snippets) and the mechanism (keyword + structural token ranking), which tells an agent it is a hybrid lexical/structural search. It does not distinguish itself from close siblings such as krusch_git_search_symbols or krusch_fs_search, so the boundary is left implicit.

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 or when-not-to-use guidance and no mention of alternatives. An agent must infer that this is the broad/fuzzy search option versus the more targeted symbol or filesystem searches, without any text saying so.

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