List available atmosphere presets and filter them by fog, mist, clouds, or haze categories, or search by keyword to find suitable presets for generative art scenes.
List available atmosphere presets. Filter by category (fog, mist, clouds, haze) or search by keyword.
| Name | Required | Description | Default |
|---|---|---|---|
| search | No | Search presets by name, description, or tags | |
| category | No | Filter by category |
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral burden. It implies a read-only list operation and names category values, but it does not disclose return format, pagination, ordering, or whether results are filtered by workspace or sketch.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with the core action front-loaded and filter options following. The category list partly duplicates the schema enum, but the description remains efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple: two optional parameters, no output schema, and full schema coverage. The description covers the basic operation but omits what an atmosphere preset is, what a returned result contains, and whether listing is scoped to the current sketch.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents both parameters and their meanings. The description repeats the category enum and mentions keyword search, adding little beyond the schema except framing the parameters as filtering options.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: list atmosphere presets. This clearly separates it from design_add_atmosphere, design_create_atmosphere, and other preset-list tools. It does not explicitly name a sibling alternative, so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when browsing presets via filtering or search. It does not specify when to use this versus design_list_particle_presets or design_list_terrain_presets, nor does it mention prerequisites or follow-up actions such as applying a selected preset.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.