Skip to main content
Glama

list_controls

Retrieve available Draugr security controls with what each checks, its backing scanner, and component or project scope so you enable valid controls before writing a Saga descriptor.

Instructions

List the security controls Draugr can run: what each one checks, which scanner backs it, and whether it applies per component or to the whole project. Call this before writing or editing a Saga descriptor, so the controls you enable are ones that exist.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
hintYes
controlsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.160.0
    • changedOutput schema / properties / controls / items / properties / optInScanners / description
      Previous value: -"additional scanners, each enabled explicitly under controllers.<control>.<scanner>.enabled"New value: +"additional scanners, each enabled explicitly under config.controls.<control>.<scanner>.enabled"
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. 'List' implies a read-only operation and the description discloses the kind of information returned, but it does not explicitly state side effects, auth requirements, or rate-limit behavior. For a simple zero-parameter list tool this is adequate, but not rich.

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 description is two tightly written sentences with no wasted words. Purpose and return content are front-loaded, followed immediately by the key usage instruction. It is appropriately sized for a simple list tool.

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?

The tool takes no parameters and has an output schema, so the description does not need to enumerate return fields or parameter details. It covers what the tool lists, what the agent will learn, and when to call it. Nothing critical is missing for correct invocation.

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?

This tool has zero parameters, so parameter semantics are inherently minimal. The description correctly avoids introducing nonexistent inputs. Baseline for zero parameters is 4.

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: list the security controls Draugr can run. It also previews the returned fields, which helps an agent understand what kind of controls these are. Sibling differentiation is only implicit through the word 'controls' and the Saga workflow context, so it falls short of a perfect 5.

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?

It explicitly says to call this before writing or editing a Saga descriptor and explains the reason: so enabled controls are ones that exist. That gives clear usage context. It does not name when-not-to-use conditions or specific alternative tools, so it is not a 5.

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