Skip to main content
Glama

list_rules

Lists every scanner rule, including its ID, severity, description, and remediation advice, so you can see what the security scan covers.

Instructions

列出扫描器的全部规则(规则 id、严重度、说明、修复建议),用于判断这套扫描覆盖什么

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_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full descriptive burden. It does disclose the shape of the returned data (id, severity, description, fix recommendation) and that the operation returns the full rule set, which is useful. It does not mention ordering, whether rules can change over time, or the approximate size of the list.

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?

A single sentence with the resource and returned fields front-loaded, followed by the purpose clause. There is no redundant phrasing and no filler.

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?

There is no output schema, so the description correctly lists the returned fields to compensate, and it gives the agent enough information to decide to call it. Minor gaps remain about list size and whether the output is stable, but for a zero-parameter read tool this is close to sufficient.

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 takes zero parameters, so no parameter semantics are needed and the baseline of 4 applies. The description correctly adds no parameter discussion and instead spends its space on what is returned.

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 gives a specific verb and resource ('列出扫描器的全部规则') and enumerates the returned fields (规则 id、严重度、说明、修复建议), plus a stated purpose ('判断这套扫描覆盖什么'). It is clear what it does, but it does not explicitly contrast with the sibling explain_rule, which is the closest alternative for rule-level information.

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 intended use case is implied by '用于判断这套扫描覆盖什么', which tells an agent this is a discovery and overview step. However, there is no explicit guidance about when to use list_rules versus explain_rule, or whether it should be called before or after a scan.

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