Skip to main content
Glama
Parado-xy

Seroost Search MCP Server

by Parado-xy

seroost_set_index

Configure the root directory for semantic code search indexing to enable natural language queries across your codebase.

Instructions

Configure the target directory for Seroost indexing. This sets the root path that will be indexed when the index command is run. Must be called before indexing to specify which codebase directory to search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to the directory containing the codebase to index. This directory and all its subdirectories will be searchable after indexing.

Implementation Reference

  • Core handler function that executes the tool logic by spawning the 'seroost' binary with arguments ['-i', path] via runSeroost.
    export function setIndex(path: string){
        const args = ['-i', path];
    
        return runSeroost(args)
    }
  • Zod input schema defining the 'path' parameter as a string with description.
    {
      path: z
        .string()
        .describe(
          "Absolute path to the directory containing the codebase to index. This directory and all its subdirectories will be searchable after indexing."
        ),
    },
  • src/index.ts:54-87 (registration)
    Full MCP server.tool registration for 'seroost_set_index', including name, description, schema, and thin async handler wrapper that delegates to setIndex.
    server.tool(
      "seroost_set_index",
      "Configure the target directory for Seroost indexing. This sets the root path that will be indexed when the index command is run. Must be called before indexing to specify which codebase directory to search.",
      {
        path: z
          .string()
          .describe(
            "Absolute path to the directory containing the codebase to index. This directory and all its subdirectories will be searchable after indexing."
          ),
      },
      async ({ path }) => {
        try {
          let output = await setIndex(path);
    
          return {
            content: [
              {
                type: "text",
                text: output ? "success" : "no output returned",
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: "failure",
              },
            ],
          };
        }
      }
    );
  • Helper utility function that spawns the 'seroost' child process, captures stdout/stderr, and resolves with output on success.
    function runSeroost(args: string[]) {
      return new Promise((resolve, reject) => {
        const proc = spawn("seroost", args);
        let out = "";
        let err = "";
    
        proc.stdout.on("data", (d) => (out += d.toString()));
        proc.stderr.on("data", (d) => (err += d.toString()));
    
        proc.on("close", (code) => {
          if (code === 0) {
            try {
              resolve(out);
            } catch {
              reject(new Error("Invalid JSON from Seroost: " + out));
            }
          } else {
            reject(new Error(err || "Seroost failed"));
          }
        });
      });
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the tool configures a directory for indexing, implying a write/mutation operation, but doesn't disclose behavioral details like whether this overwrites previous settings, requires specific permissions, or has side effects. The description adds basic context about the tool's role in the indexing process but lacks richer behavioral transparency.

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 two sentences, front-loaded with the core purpose, followed by a crucial usage guideline. Every sentence earns its place by providing essential information without redundancy or fluff, making it highly efficient and well-structured.

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 tool's moderate complexity (a configuration step with one parameter), no annotations, and no output schema, the description is largely complete. It explains the purpose, usage timing, and relationship to other tools. However, it could improve by mentioning what happens if called multiple times or error conditions, slightly reducing completeness.

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 100%, so the schema already fully documents the single 'path' parameter. The description adds no additional parameter semantics beyond what the schema provides (e.g., no extra syntax, format, or usage details), meeting the baseline score when schema coverage is high.

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 the specific action ('Configure the target directory') and resource ('Seroost indexing'), distinguishing it from sibling tools like 'seroost_index' (which presumably runs indexing) and 'seroost_search' (which searches the index). It explicitly defines the tool's role in setting the root path for indexing operations.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: 'Must be called before indexing to specify which codebase directory to search.' This clearly indicates when to use this tool (as a prerequisite step) versus its siblings, establishing a workflow sequence without ambiguity.

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/Parado-xy/semantic-search-mcp'

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