Skip to main content
Glama

List bug classes

list_categories
Read-onlyIdempotent

List bug classes in the vulnerability archive with report counts and one-line descriptions, then use their IDs to search reports or retrieve category guides.

Instructions

List the bug classes the archive is organized into (XSS, SSRF, IDOR, request smuggling…), with report counts and a one-line description. Use the ids with search_reports(category=…) and get_category_guide.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description adds crucial behavioral context by specifying that the output includes report counts and a one-line description, which goes beyond the structural hints provided in the annotations.

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?

The definition is highly efficient; it uses two sentences to define scope, detail the output, and guide subsequent usage without unnecessary filler.

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 that the tool takes no parameters and has no defined output schema, the description is maximally complete by defining what the user receives and how that output should be processed using sibling tools.

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?

Since the tool accepts zero parameters and the schema coverage is 100%, the description has no semantic content to add regarding input fields. It meets the baseline expectation for this case.

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 immediately defines the purpose as listing bug classes and specifies the content provided (report counts and one-line descriptions), clearly distinguishing it from tools that search or retrieve specific reports.

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?

It provides explicit instructions on how to use the output, directing the agent to utilize the returned IDs with the sibling tools search_reports and get_category_guide.

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