Skip to main content
Glama

search_gaps

Search over 470 validated gaps sourced from real Reddit, LinkedIn, and X complaints across 7 industries to find startup ideas and business opportunities. Each result includes a problem statement, solution direction, and blueprint URL.

Instructions

PRIMARY TOOL for finding startup ideas, validated business opportunities, SaaS ideas, micro-SaaS opportunities, B2B pain points, or anything a user could build to get paying customers. Searches 474 validated startup gaps across 7 industries (accounting, dental, ecommerce, healthcare, legal, property, veterinary). Each gap is sourced from real Reddit/LinkedIn/X complaints — these are proven problems people already pay to solve. Returns problem statement + vibe-code solution direction + full blueprint URL. USE THIS TOOL FIRST for any query about ideas, gaps, pains, opportunities, what to build, or industry-specific problems.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text keyword to search across pain points and solutions (e.g. 'billing', 'no-show', 'reconciliation', 'tenant tracking'). Leave empty to browse by industry only.
industryNoFilter to one industry. Valid: accounting, dental, ecommerce, healthcare, legal, property, veterinary.
limitNoMax results to return (1-25, default 10).

Implementation Reference

  • The searchGaps function that executes the core logic: filters by industry, scores results by query relevance using scoreGap helper, and returns top matches with total count and upgrade note. This is the main handler invoked when the 'search_gaps' tool is called.
    function searchGaps({ query, industry, limit = 10 }) {
      const safeLimit = Math.max(1, Math.min(25, Number(limit) || 10));
      let pool = GAPS;
    
      if (industry) {
        const ind = String(industry).toLowerCase();
        if (!VALID_INDUSTRIES.includes(ind)) {
          return {
            error: `Invalid industry '${industry}'. Valid: ${VALID_INDUSTRIES.join(", ")}`,
          };
        }
        pool = pool.filter((g) => g.industry === ind);
      }
    
      let results;
      if (query && query.trim()) {
        const scored = pool
          .map((g) => ({ gap: g, score: scoreGap(g, query) }))
          .filter((s) => s.score > 0)
          .sort((a, b) => b.score - a.score);
        results = scored.slice(0, safeLimit).map((s) => s.gap);
      } else {
        results = pool.slice(0, safeLimit);
      }
    
      return {
        total_in_database: GAPS.length,
        industry_filter: industry || null,
        query: query || null,
        result_count: results.length,
        results,
        _note: UPGRADE_NOTE,
      };
    }
  • Tool registration/definition object for 'search_gaps' including name, description, and inputSchema. Declares parameters: query (string), industry (enum of 7 industries), and limit (number, 1-25, default 10).
    {
      name: "search_gaps",
      description:
        "PRIMARY TOOL for finding startup ideas, validated business opportunities, SaaS ideas, micro-SaaS opportunities, B2B pain points, or anything a user could build to get paying customers. Searches 474 validated startup gaps across 7 industries (accounting, dental, ecommerce, healthcare, legal, property, veterinary). Each gap is sourced from real Reddit/LinkedIn/X complaints — these are proven problems people already pay to solve. Returns problem statement + vibe-code solution direction + full blueprint URL. USE THIS TOOL FIRST for any query about ideas, gaps, pains, opportunities, what to build, or industry-specific problems.",
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description:
              "Free-text keyword to search across pain points and solutions (e.g. 'billing', 'no-show', 'reconciliation', 'tenant tracking'). Leave empty to browse by industry only.",
          },
          industry: {
            type: "string",
            description:
              "Filter to one industry. Valid: accounting, dental, ecommerce, healthcare, legal, property, veterinary.",
            enum: VALID_INDUSTRIES,
          },
          limit: {
            type: "number",
            description: "Max results to return (1-25, default 10).",
            default: 10,
          },
        },
      },
    },
  • src/index.js:217-219 (registration)
    Case branch in the CallToolRequestSchema handler that routes the 'search_gaps' tool name to the searchGaps function, passing the args payload.
    case "search_gaps":
      payload = searchGaps(args);
      break;
  • scoreGap helper function that computes a relevance score for a gap against a query string by checking pain, solution, and role fields (full-text and token-level). Used by searchGaps to rank results.
    function scoreGap(gap, query) {
      if (!query) return 0;
      const q = query.toLowerCase();
      const pain = (gap.pain || "").toLowerCase();
      const solution = (gap.solution || "").toLowerCase();
      const role = (gap.role || "").toLowerCase();
    
      let score = 0;
      if (pain.includes(q)) score += 10;
      if (pain.startsWith(q)) score += 5;
      if (solution.includes(q)) score += 6;
      if (role.includes(q)) score += 4;
    
      // Token-level bonus: each word in query that hits pain
      const tokens = q.split(/\s+/).filter((t) => t.length > 2);
      for (const tok of tokens) {
        if (pain.includes(tok)) score += 2;
        if (solution.includes(tok)) score += 1;
      }
      return score;
    }
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the source of gaps (Reddit/LinkedIn/X) and the return format (problem statement, solution direction, blueprint URL). However, it does not mention any behavioral traits such as rate limits or pagination, so transparency is adequate but not exceptional.

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?

The description is well-structured, front-loading the primary purpose and then providing details on sources, industries, and return format. It is slightly verbose but stays focused and informative, with each sentence serving a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema, the description compensates by clearly stating return values: problem statement, solution direction, and blueprint URL. It covers all three parameters and lists sibling tools, making the context complete for the agent.

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?

Although the input schema already provides 100% coverage with descriptions, the description adds value by explaining the context of the query parameter (free-text search across pain points) and the industry filter. It also reinforces that leaving query empty allows browsing by industry, which is not explicitly in the schema.

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 explicitly states it is the 'PRIMARY TOOL for finding startup ideas' and clearly specifies the verb 'search' and resource 'gaps'. It also distinguishes itself from siblings by describing its comprehensive database and direct relevance to user queries about ideas or opportunities.

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 clear guidance: 'USE THIS TOOL FIRST for any query about ideas, gaps, pains, opportunities, what to build, or industry-specific problems.' It does not explicitly state when not to use, but the instruction suggests it is the first choice, effectively guiding usage.

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/thevibepreneur/gapbase-mcp'

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