Skip to main content
Glama
Sign In
SSW Rules MCP

SSW Rules MCP

by SSWConsulting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Categories

list_categories

Retrieve all SSW Rules categories with subcategories and rule counts. Use it to browse the rule hierarchy and locate best-practice topics by category.

Instructions

List all SSW Rules categories in the hierarchy.

Returns top-level categories (e.g. Software Engineering, Communication) with their subcategories and rule counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the shape of the result (top-level categories, subcategories, rule counts), which signals a read-only listing operation, but it says nothing about ordering, caching, or completeness guarantees — reasonable but not rich for a zero-parameter read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core action front-loaded and the return shape second. No filler, though the second sentence partially restates what the output schema already conveys.

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?

An output schema exists, so return values need not be re-explained, and there are no parameters to cover. The definition is nearly complete for such a simple tool; the missing piece is any hint of when to prefer it over get_category_rules.

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 per the baseline there is nothing for the description to document. No misleading parameter language is present.

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?

States a specific verb and resource ('List all SSW Rules categories in the hierarchy') and clarifies the granularity by explaining it returns top-level categories with subcategories and rule counts. It is clearly distinguishable from get_category_rules in practice, but it never names or contrasts a sibling explicitly.

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

Usage Guidelines2/5

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

No when-to-use guidance is given. The description does not mention that this is a discovery/navigation step before calling get_category_rules, nor does it state any conditions or alternatives. Usage is only inferable from the tool name.

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