Skip to main content
Glama

list_presets

Lists available Mcp-Warden presets—named, scoped actions—with types, approval policies, and SSH command parameters so agents can pick the right action while keeping secrets protected.

Instructions

List available mcp-warden presets — named, scoped actions you may invoke. Returns name, description, type (http|ssh|postgres|mysql|redis), and approval policy (auto|prompt|deny); for SSH presets, also their named commands with what each parameter accepts. Read-only; never returns secret values. Use proxy_http for HTTP actions, ssh_run for named commands, and get_secret_for_env only as a last resort when a child process must read a secret from its environment.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
presetsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • addedOutput schema / $defs / CommandSummary
      Added value: +{
      +  "properties": {
      +    "approval": {
      +      "description": "This command's policy: \"auto\", \"prompt\", or \"deny\".",
      +      "type": "string"
      +    },
      +    "description": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "params": {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "description": "What each parameter accepts, e.g. `int from 1 to 500`.",
      +      "type": "object"
      +    },
      +    "template": {
      +      "description": "The command line, with `{param}` where each value goes.",
      +      "type": "string"
      +    },
      +    "tool": {
      +      "description": "Also offered as its own tool under this name (`expose_as_tools`).",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "description",
      +    "template",
      +    "params",
      +    "approval"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / $defs / PresetSummary / properties / commands
      Added value: +{
      +  "description": "SSH: the named commands `ssh_run` runs. Absent: none.",
      +  "items": {
      +    "$ref": "#/$defs/CommandSummary"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / $defs / PresetSummary / properties / kind / description
      Previous value: -"\"http\" or \"ssh\"."New value: +"\"http\", \"ssh\", \"postgres\", \"mysql\" or \"redis\"."
    • changedOutput schema / $defs / PresetSummary / required
      Previous value: -[
      -  "name",
      -  "description",
      -  "kind",
      -  "approval"
      -]New value: +[
      +  "name",
      +  "description",
      +  "kind",
      +  "approval",
      +  "commands"
      +]
  2. Changed1 schema field changedv0.5.2
    • addedOutput schema / $defs / PresetSummary / properties / expires_at
      Added value: +{
      +  "description": "When access through this preset ends (RFC 3339). Absent: no limit.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden — and it does so well by declaring 'Read-only; never returns secret values', which is exactly the safety signal an agent needs for a credential-adjacent listing tool. It also discloses the shape of the response (type enum, approval policy values, SSH named commands). It stops short of stating authentication requirements or whether results are scoped to the caller's permissions.

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?

Front-loaded with purpose, then return contents, then safety, then routing — a sensible order with no filler sentences. Slight over-allocation to enumerating return fields that an output schema may already cover, but nothing is gratuitous.

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?

For a zero-parameter discovery tool, the description covers purpose, what comes back, safety profile, and where to go next — everything needed to invoke it correctly. Return-field enumeration is mildly redundant given the output schema exists, but that is surplus rather than a gap.

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 there is nothing for the description to disambiguate; the schema baseline of 4 applies. The description correctly spends no words on nonexistent inputs.

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 and resource ('List available mcp-warden presets') and immediately defines what a preset is ('named, scoped actions you may invoke'), then enumerates the returned fields and type enum values. An agent can distinguish this discovery tool from the execution siblings without opening any 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?

Explicitly routes the agent to the right alternatives with conditions: 'Use `proxy_http` for HTTP actions, `ssh_run` for named commands, and `get_secret_for_env` only as a last resort when a child process must read a secret from its environment.' That names three siblings and the circumstances selecting each, which is the strongest form of this guidance.

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