Skip to main content
Glama

get_stats

Retrieve comprehensive GapBase statistics including total gaps, industry breakdown, and trending gap counts to understand the startup gap landscape.

Instructions

Get GapBase database statistics: total gaps, industry breakdown, trending gap count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getStats function that executes the tool logic. Returns an object with total_gaps, industries (via industryCounts()), viral_social_gaps count, database name, website URL, source, and an upgrade note.
    function getStats() {
      return {
        total_gaps: GAPS.length,
        industries: industryCounts(),
        viral_social_gaps: TRENDS.length,
        database: "GapBase",
        website: "https://thevibepreneur.com",
        source: "Validated pain points from Reddit, LinkedIn, and X.",
        _note: UPGRADE_NOTE,
      };
    }
  • Tool schema registration for 'get_stats' in the TOOLS array. Defines name, description, and inputSchema (empty object, no parameters required).
    {
      name: "get_stats",
      description:
        "Get GapBase database statistics: total gaps, industry breakdown, trending gap count.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.js:229-232 (registration)
    Tool dispatch in the CallToolRequestSchema handler. When name is 'get_stats', calls getStats() and assigns the result to payload.
      break;
    case "get_stats":
      payload = getStats();
      break;
  • Helper function industryCounts() used by getStats to compute the per-industry gap counts from the GAPS array.
    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);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits like auth requirements, rate limits, or read-only nature. The listed statistics give some idea of output but no side effects or safety info.

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?

Single sentence, front-loaded with key information. Every word contributes: verb (Get), resource (GapBase database statistics), specific outputs (total gaps, industry breakdown, trending gap count). No wasted text.

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, no-output-schema tool, the description is nearly complete. It covers the tool's purpose and data categories. However, missing details on output format, caching, or how results relate to sibling tools keep it from being fully comprehensive.

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?

There are no parameters, so the description cannot add parameter meaning. Baseline 4 is appropriate given 100% schema coverage and zero params; description correctly omits param details.

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 tool retrieves database statistics, specifying three distinct types (total gaps, industry breakdown, trending gap count). This verb-resource pairing is specific and distinguishes it from siblings like get_gap (single gap) or list_industries (industry list).

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

Usage Guidelines3/5

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

The description implies usage for overview statistics but provides no explicit guidance on when to use this tool vs alternatives. No exclusions or prerequisites are mentioned, leaving the agent to infer context from sibling names.

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