Skip to main content
Glama

skvil_stats

Retrieve aggregate statistics from the Skvil community network, including total skills scanned, trusted count, critical findings, and certified skills for security verification.

Instructions

Get aggregate statistics from the Skvil community network: total skills scanned, trusted count, critical findings, and certified skills.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.ts:120-146 (registration)
    Tool registration and handler for skvil_stats. Registers the tool with the MCP server and defines the async handler that calls api.stats() and formats the response as readable text showing total skills scanned, trusted count, critical findings, and certified skills.
    // ── skvil_stats ───────────────────────────────────────────────────────────
    server.tool(
      'skvil_stats',
      'Get aggregate statistics from the Skvil community network: total skills ' +
        'scanned, trusted count, critical findings, and certified skills.',
      {},
      async () => {
        try {
          const result = await api.stats();
          return {
            content: [
              {
                type: 'text',
                text:
                  '**Skvil community statistics**\n\n' +
                  `- **Total skills scanned:** ${result.total}\n` +
                  `- **Trusted** (reputation >= 70): ${result.trusted}\n` +
                  `- **Critical findings:** ${result.critical}\n` +
                  `- **Certified:** ${result.certified}`,
              },
            ],
          };
        } catch (error) {
          return { content: [{ type: 'text', text: formatError('stats', error) }], isError: true };
        }
      },
    );
  • Core API function that makes the HTTP GET request to the /stats endpoint. Returns a Promise<StatsResponse> with the statistics data.
    /** Get community statistics. */
    export async function stats(): Promise<StatsResponse> {
      return request<StatsResponse>('GET', '/stats');
    }
  • Type definition for the StatsResponse interface that defines the structure of the data returned from the /stats API endpoint, including total skills, trusted count, critical findings, and certified skills count.
    export interface StatsResponse {
      total: number;
      trusted: number;
      critical: number;
      certified: number;
    }
Behavior2/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 of behavioral disclosure. It states this is a 'Get' operation, implying it's likely read-only, but doesn't confirm this or mention other traits like authentication needs, rate limits, or what happens if the network is unavailable. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that front-loads the purpose and lists key metrics. It avoids redundancy and wastes no words, though it could be slightly more structured by explicitly noting the lack of parameters or differentiating from siblings.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It explains what statistics are retrieved, but without annotations or output schema, it doesn't cover behavioral aspects like safety or return format. For a read-only stats tool, this is minimally viable but incomplete.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, but it implicitly confirms this by not mentioning any parameters, aligning with the schema. Baseline is 4 for 0 parameters, as no compensation is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('aggregate statistics from the Skvil community network'), listing the specific metrics returned. However, it doesn't explicitly differentiate this statistical retrieval tool from its siblings like skvil_report or skvil_scan, which might also involve data retrieval.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like skvil_report and skvil_scan that might involve reporting or scanning data, there's no indication of when this aggregate statistics tool is preferred over those options, nor any prerequisites or exclusions mentioned.

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/Skvil-IA/skvil-mcp'

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