Skip to main content
Glama

skvil_certified

View verified and certified AI agent skills with tamper-proof blockchain verification. Shows recently certified skills with their level, reputation score, and certification date.

Instructions

List skills that have been verified and certified by Skvil admins. Certified skills have been manually reviewed and registered for tamper-proof verification. Returns up to 10 most recently certified skills with their level (V1/V2/V3/Gold), reputation score, and certification date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.ts:148-194 (registration)
    Tool registration and handler implementation for 'skvil_certified'. Registers the tool with the MCP server, defines its description, and implements the async handler that calls api.certified() and formats the response with skill names, certification levels, reputation scores, scan counts, and certification dates.
    // ── skvil_certified ───────────────────────────────────────────────────────
    server.tool(
      'skvil_certified',
      'List skills that have been verified and certified by Skvil admins. ' +
        'Certified skills have been manually reviewed and registered for ' +
        'tamper-proof verification. Returns up to 10 most recently certified ' +
        'skills with their level (V1/V2/V3/Gold), reputation score, and ' +
        'certification date.',
      {},
      async () => {
        try {
          const result = await api.certified();
    
          if (result.length === 0) {
            return {
              content: [
                {
                  type: 'text',
                  text: 'No skills are currently certified. Be the first to get certified!',
                },
              ],
            };
          }
    
          const lines = ['**Certified skills**\n'];
    
          for (const skill of result) {
            lines.push(
              `- **${skill.name}** — ${skill.level} | Score: ${formatScore(skill.reputation_score)} | ` +
                `${skill.total_scans} scans | Certified: ${skill.certified_at}\n` +
                `  Hash: \`${skill.composite_hash}\``,
            );
          }
    
          lines.push(
            '\nAll certifications are registered for tamper-proof, publicly verifiable trust.',
          );
    
          return { content: [{ type: 'text', text: lines.join('\n') }] };
        } catch (error) {
          return {
            content: [{ type: 'text', text: formatError('certified', error) }],
            isError: true,
          };
        }
      },
    );
  • API helper function that makes the HTTP GET request to the '/certified' endpoint to retrieve the list of certified skills from the Skvil server.
    /** List actively certified skills. */
    export async function certified(): Promise<CertifiedSkill[]> {
      return request<CertifiedSkill[]>('GET', '/certified');
    }
  • Type definition for the CertifiedSkill interface that defines the structure of the response data, including name, composite_hash, certification level (V1/V2/V3/Gold), reputation_score, certified_at timestamp, and total_scans.
    export interface CertifiedSkill {
      name: string;
      composite_hash: string;
      level: 'V1' | 'V2' | 'V3' | 'Gold';
      reputation_score: number;
      certified_at: string;
      total_scans: number;
    }
  • Helper function formatScore used by the skvil_certified handler to format reputation scores with safety indicators (safe, caution, danger).
    function formatScore(score: number): string {
      if (score >= 80) return `${score.toFixed(1)} (safe)`;
      if (score >= 50) return `${score.toFixed(1)} (caution)`;
      return `${score.toFixed(1)} (danger)`;
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden and adds valuable behavioral context: it discloses that results are limited to 'up to 10 most recently certified skills' (implying a limit and recency ordering), and details the return fields (level, reputation score, certification date). It does not mention permissions or rate limits, but provides clear output expectations.

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?

The description is front-loaded with the core purpose in the first sentence, followed by additional context in a second sentence. Every sentence adds value: the first defines the action and resource, the second explains certification and specifies return details. It is appropriately sized with zero waste.

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?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is complete enough: it explains what the tool does, the scope of results, and the return format. It could improve by mentioning any prerequisites or error cases, but for a simple list tool, it covers essential context adequately.

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 no parameter documentation is needed. The description appropriately does not discuss parameters, maintaining focus on the tool's purpose and output. Baseline is 4 for 0 parameters, as it avoids unnecessary 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 specific action ('List skills that have been verified and certified by Skvil admins') and resource ('certified skills'), distinguishing it from siblings like 'skvil_register' (likely for registration) or 'skvil_verify' (likely for verification processes). It specifies the scope of 'certified' skills versus other types.

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 retrieving certified skills with details like level and date, but does not explicitly state when to use this tool versus alternatives such as 'skvil_catalog' (which might list all skills) or 'skvil_stats' (which might provide statistics). It provides context but lacks explicit guidance on exclusions or comparisons.

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