Skip to main content
Glama
radiovisual

zoekt-mcp

by radiovisual

search_code

Search indexed code repositories using Zoekt queries with filters for repository, file, language, symbol, and regex to find matching code files and snippets.

Instructions

Run a Zoekt query against the indexed corpus.

    Query syntax highlights:

    - ``repo:NAME`` restrict to repos whose name matches NAME (regex)
    - ``file:PATH`` restrict to files whose path matches PATH (regex)
    - ``lang:LANGUAGE`` restrict to a language (``python``, ``go``, ...)
    - ``sym:IDENT`` match symbol definitions (functions, classes, ...)
    - ``case:yes`` case-sensitive content match
    - ``/regex/`` regex content match (literal match by default)
    - whitespace is AND; use ``or`` for boolean OR

    Examples:

    - ``lang:python def hello`` — Python files containing ``def hello``
    - ``sym:users`` — anything that defines a ``users`` symbol
    - ``repo:flask-app file:app.py`` — within one file of one repo

    Returns a compact object with ``files`` (each containing ``repo``,
    ``file``, ``language``, and ``matches``) plus top-level stats.
    Results are capped at ``max_results`` files.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo
context_linesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description explains that results are capped at max_results and returns a compact object with files and stats. Since no annotations are provided, it carries the full burden; it is mostly transparent about the read-only nature and output structure, though it could mention authentication or rate limits.

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?

The description is well-structured with bullet points and examples, front-loading the purpose. Every sentence adds value, and it is appropriately sized for the tool's complexity.

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?

Given the existence of an output schema, the description adequately describes the return structure. It comprehensively covers query syntax but misses explaining the 'context_lines' parameter, and does not address error scenarios.

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 0%, so the description must compensate. It thoroughly explains the 'query' parameter syntax but offers minimal detail on 'max_results' (only that results are capped) and no detail on 'context_lines'.

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 clearly states 'Run a Zoekt query against the indexed corpus,' which is a specific verb-resource combination. It distinguishes itself from sibling tools 'get_file' and 'list_repos' by focusing on search across repos.

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

Usage Guidelines4/5

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

The description provides detailed query syntax and examples, guiding effective use. However, it does not explicitly contrast with sibling tools or specify when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/radiovisual/zoekt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server