Skip to main content
Glama

squirrelscan

by com.squirrelscan
OverviewDiscussionsAdmin

List audit rules

list_rules
Read-only

Browse the catalog of 300+ audit rules that run during an audit, grouped into categories (crawlability, meta tags, performance, security, accessibility, content, and more). Filter by category code or search by keyword to find what a specific rule checks. Use get_rule for one rule's full detail.

Input Schema

NameRequiredDescriptionDefault
searchNoCase-insensitive keyword match on rule id, name, and description.
categoryNoFilter to one category code (see the categories list in the response).
include_categoriesNoInclude the categories list (code, name, rule_count). Default: included only when no category or search filter is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties / include_categories
      Added value: +{
+  "description": "Include the categories list (code, name, rule_count). Default: included only when no category or search filter is given.",
+  "type": "boolean"
+}
  2. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that – catalog scale (300+ rules), the category groupings, and the fact that it lists rather than retrieves detail. It doesn't discuss pagination or result limits, but for a read-only listing the added data-structure context is solid.

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?

Three sentences, front-loaded with the tool's scope, then filtering options, then the sibling hand-off. No filler and every sentence carries routing or scoping information.

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?

With no output schema, the description usefully conveys what is returned (rules grouped into categories, with a categories list) and how to narrow results. Combined with the sibling routing to get_rule, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters (search, category, include_categories) are already documented in the schema. The description reinforces category-code and keyword filtering but adds no syntax, format, or semantics beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb+resource ('browse the catalog of 300+ audit rules') and immediately scopes it as a catalog/listing tool. It explicitly differentiates from the sibling get_rule ('Use get_rule for one rule's full detail'), so an agent can pick the right tool without opening either schema.

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

Usage Guidelines5/5

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

Gives clear selection guidance: filter by category code or search by keyword to locate a rule, and names the alternative get_rule for single-rule detail. The when-to-use and the alternative are both explicit, leaving nothing to inference.

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

All squirrelscan toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources