Skip to main content
Glama
Sign In
openclaw-skill-vetter-mcp

openclaw-skill-vetter-mcp

by temurkhan13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_detection_rules

Retrieve all detection rules applied by the security vetter, including rule IDs, severities, and descriptions, to understand which checks are performed.

Instructions

Return the catalog of every detection rule this server applies, with rule IDs, severities, and descriptions. Use this to understand what the vetter checks (and what it doesn't).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_detection_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Describes the output fields (rule IDs, severities, descriptions) and implies a read-only operation without side effects. No annotations exist, so the description carries the burden, and it adequately conveys the tool's behavior.

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-load the action and result. Every word adds value, with no redundancy.

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 no parameters or output schema, the description fully covers the tool's purpose and output, making it complete for an agent to select and use correctly.

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 schema coverage is 100%. The description does not need to add parameter meaning, and the baseline for zero parameters is 4.

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 returns a catalog of detection rules with IDs, severities, and descriptions. It distinguishes from sibling tools by focusing on the overall rule set rather than specific scanning or vetting operations.

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?

Explicitly advises to use this tool to understand what the vetter checks and what it doesn't, providing clear context for when to invoke it. While it doesn't list alternatives or exclusions, the guideline is sufficient for a zero-parameter list tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools