Skip to main content
Glama
Parado-xy

Seroost Search MCP Server

by Parado-xy

seroost_index

Builds a searchable index for codebases by processing all files in a configured directory, enabling fast semantic searches with natural language queries.

Instructions

Build the search index for the previously configured directory path. This processes all files in the target directory and creates a searchable index. Must run after setting the index path with seroost_set_index. Indexing may take time for large codebases but enables fast subsequent searches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:89-116 (registration)
    Registration of the 'seroost_index' MCP tool, including empty input schema and inline handler function that invokes runIndex() from commands.ts and returns formatted success/failure response.
    server.tool(
      "seroost_index",
      "Build the search index for the previously configured directory path. This processes all files in the target directory and creates a searchable index. Must run after setting the index path with seroost_set_index. Indexing may take time for large codebases but enables fast subsequent searches.",
      {}, // No parameters needed - uses the path set by seroost_set_index
      async () => {
        try {
          let output = await runIndex();
    
          return {
            content: [
              {
                type: "text",
                text: output ? "success" : "no output returned",
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: "failure",
              },
            ],
          };
        }
      }
    );
  • Inline handler function for seroost_index tool execution: awaits runIndex(), handles errors, returns MCP content block with status.
    async () => {
      try {
        let output = await runIndex();
    
        return {
          content: [
            {
              type: "text",
              text: output ? "success" : "no output returned",
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: "failure",
            },
          ],
        };
      }
    }
  • runIndex helper: prepares 'index' arguments and calls runSeroost to spawn the seroost binary for indexing.
    export function runIndex() {
      const args = ["index"];
    
      return runSeroost(args);
    }
  • runSeroost utility: spawns child_process 'seroost' CLI with args, streams stdout/stderr, resolves with output on success (code 0), rejects on error.
    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"));
          }
        });
      });
    }
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a processing operation that creates a searchable index, has a prerequisite dependency on another tool, may have significant execution time for large inputs, and enables subsequent fast searches. It doesn't mention error conditions or specific performance characteristics, keeping it from a perfect score.

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?

Three well-structured sentences with zero waste: first states the core purpose, second explains the processing scope and output, third provides crucial usage guidance and performance context. Every sentence earns its place by adding distinct value.

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?

For a zero-parameter tool with no annotations or output schema, the description provides excellent context about purpose, prerequisites, behavioral characteristics, and relationship to siblings. It doesn't specify exact return values or error conditions, but given the tool's simplicity, this is reasonably complete.

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

Parameters4/5

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

The tool has zero parameters with 100% schema description coverage, so the baseline would be 4. The description adds value by explaining that parameters come from 'previously configured directory path' set via 'seroost_set_index', providing important context about how configuration flows between tools.

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 ('Build the search index'), resource ('previously configured directory path'), and scope ('processes all files in the target directory'). It distinguishes from sibling tools by mentioning the prerequisite relationship with 'seroost_set_index' and contrasting with 'seroost_search' through its indexing function.

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?

Explicitly states when to use ('Must run after setting the index path with seroost_set_index') and provides context about alternatives by contrasting with 'seroost_search' (this tool builds the index while the sibling searches it). It also gives practical guidance about timing considerations ('may take time for large codebases').

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