Skip to main content
Glama
temurkhan13

openclaw-skill-vetter-mcp

by temurkhan13

vet_skill_directory

Audit installed skills by running all security scanners on each skill in the directory, generating an aggregate report with per-skill findings and risk level counts.

Instructions

Run all scanners on every skill in the configured directory and return an aggregate report (per-skill VetReports + counts by risk level). Use this for a periodic audit of installed skills.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function: vets every skill in a directory and aggregates results into a DirectoryVetReport. Calls vet_skill() for each skill, sorts by risk_score descending, and counts by risk level.
    def vet_skill_directory(skills: list[Skill], directory: str) -> DirectoryVetReport:
        """Vet every skill in a directory and aggregate."""
        reports = [vet_skill(s) for s in skills]
        reports.sort(key=lambda r: r.risk_score, reverse=True)
    
        by_level = Counter(r.risk_level for r in reports)
        return DirectoryVetReport(
            captured_at=datetime.now(UTC),
            directory=directory,
            skill_count=len(reports),
            skills=reports,
            aggregate_block_count=by_level[RiskLevel.BLOCK],
            aggregate_review_count=by_level[RiskLevel.REVIEW],
            aggregate_caution_count=by_level[RiskLevel.CAUTION],
            aggregate_clean_count=by_level[RiskLevel.CLEAN],
            aggregate_unknown_count=by_level[RiskLevel.UNKNOWN],
        )
  • DirectoryVetReport model: the return type of vet_skill_directory, containing captured_at, directory, skill_count, per-skill VetReports, and aggregate counts by risk level.
    class DirectoryVetReport(BaseModel):
        """Aggregate report across all skills in a directory."""
    
        model_config = ConfigDict(frozen=True)
    
        captured_at: datetime
        directory: str
        skill_count: int
        skills: list[VetReport]
        """Per-skill reports, sorted by risk_score descending."""
        aggregate_block_count: int
        aggregate_review_count: int
        aggregate_caution_count: int
        aggregate_clean_count: int
        aggregate_unknown_count: int
  • Tool registration in list_tools(): defines the 'vet_skill_directory' Tool with description and empty inputSchema (no required arguments).
    Tool(
        name="vet_skill_directory",
        description=(
            "Run all scanners on every skill in the configured directory and return "
            "an aggregate report (per-skill VetReports + counts by risk level). "
            "Use this for a periodic audit of installed skills."
        ),
        inputSchema={"type": "object", "properties": {}, "required": []},
    ),
  • Tool dispatch in call_tool(): when name=='vet_skill_directory', fetches skills and directory from backend, calls vet_skill_directory(), and serializes the result.
    if name == "vet_skill_directory":
        skills = await backend.get_skills()
        directory = await backend.get_directory()
        return _serialize(vet_skill_directory(skills, directory))
  • Helper _serialize(): converts any Pydantic model to MCP TextContent (JSON-indented) for the response.
    def _serialize(model: Any) -> list[TextContent]:
        """Pydantic model → MCP TextContent (single block, JSON-serialized)."""
        return [TextContent(type="text", text=model.model_dump_json(indent=2))]
Behavior3/5

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

No annotations are provided, so the description carries the burden. It implies a read-only operation (returns report) but lacks mentions of permissions, rate limits, or potential heaviness of running all scanners.

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 sentences, direct and front-loaded, with no wasted words. Every sentence earns its place.

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 no output schema, the description adequately explains the return format as 'per-skill VetReports + counts by risk level'. It covers the main point but lacks precise structure details.

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 tool has 0 parameters, and the schema coverage is 100%. Baseline is 4 for zero-parameter tools, and the description does not need to add parameter 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 'Run all scanners on every skill in the configured directory' with a specific verb and resource, and differentiates from siblings by indicating it's a comprehensive audit, unlike 'vet_skill' which likely targets a single skill.

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 explicitly says 'Use this for a periodic audit of installed skills', providing clear context for usage. However, it does not mention when not to use or compare with alternatives like 'flagged_skills_report'.

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/temurkhan13/openclaw-skill-vetter-mcp'

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