Skip to main content
Glama

list_presets

Read-only

Lists available presets for a selected kind—layout, render, burn-in, keyboard, Fairlight, user preferences, project settings, or quick export—so agents can identify and reuse existing configurations.

Instructions

List presets of one kind: layout, render, burn_in, keyboard (with the current one), fairlight, user_preferences, project_settings or quick_export.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "list_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral detail not in the annotations, namely that the keyboard kind returns the current one, but says nothing about ordering, pagination, or what a preset entry contains.

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?

One front-loaded sentence that opens with the verb and resource, then enumerates values. It is efficient, though the value list largely duplicates the enum and could have been traded for a note on return content.

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?

For a single-parameter, read-only enumeration tool with no output schema and annotations covering safety, the description is close to sufficient. The only real gap is not hinting at what is returned about each preset (name/id) that a subsequent apply call would need.

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?

Schema coverage is 0% in prose, but the single parameter is a fully self-documenting enum, and the description restates every allowed value so the agent need not open the schema. It also adds meaning beyond the enum by noting the keyboard kind includes the current preset.

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 (List) and resource (presets) and constrains scope to exactly one kind, with the eight kinds spelled out. An agent can tell it apart from apply_fairlight_preset-style siblings, though it never explicitly says it only enumerates rather than applies.

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

Usage Guidelines3/5

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

Usage is only implied: you call it to enumerate presets of a given kind. There is no statement of when to prefer it over other listing tools (e.g. list_render_jobs) and no prerequisites or follow-up guidance such as using the returned names with apply_fairlight_preset.

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