Skip to main content
Glama

list_industries

View the 7 industries covered by Gapbase and the number of validated gaps in each to understand database coverage before searching.

Instructions

List the 7 industries covered by GapBase and the number of validated gaps in each. Use this first to understand the database coverage before searching.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'list_industries' tool. It calls the industryCounts() helper function and returns the industry breakdown along with total gap count.
    case "list_industries":
      payload = {
        industries: industryCounts(),
        total_gaps: GAPS.length,
        _note: UPGRADE_NOTE,
      };
      break;
  • src/index.js:120-129 (registration)
    Registration of the 'list_industries' tool in the TOOLS array, defining its name, description, and empty inputSchema.
    const TOOLS = [
      {
        name: "list_industries",
        description:
          "List the 7 industries covered by GapBase and the number of validated gaps in each. Use this first to understand the database coverage before searching.",
        inputSchema: {
          type: "object",
          properties: {},
        },
      },
  • The industryCounts() helper function that computes the count of gaps per industry from the GAPS data array, returning sorted results.
    function industryCounts() {
      const counts = {};
      for (const g of GAPS) {
        counts[g.industry] = (counts[g.industry] || 0) + 1;
      }
      return Object.entries(counts)
        .map(([industry, count]) => ({ industry, count }))
        .sort((a, b) => b.count - a.count);
    }
Behavior4/5

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

No annotations provided, but description accurately describes the read-only listing of industries and counts. Does not mention any potential side effects, but given the nature, none are expected.

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?

Two concise sentences, front-loaded with the action and followed by usage advice. No wasted words.

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 zero parameters and no output schema, the description fully explains the tool's purpose and provides usage context, leaving no gaps for a simple listing tool.

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?

No parameters exist; schema coverage is 100%. Description adds value by specifying the exact output content (industries and gap counts).

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?

Description clearly states it lists the 7 industries and their gap counts, distinguishing it from sibling tools that handle individual gaps or searches.

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 instructs to use this first to understand database coverage before searching, providing clear when-to-use guidance.

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