still_list
List all stills in the current gallery album of DaVinci Resolve.
Instructions
List stills in the current gallery album.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
List all stills in the current gallery album of DaVinci Resolve.
List stills in the current gallery album.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits beyond the basic action. It does not state whether the tool is read-only, if it requires permissions, or if it paginates results, leaving uncertainty for the agent.
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?
The description is a single, concise sentence with no unnecessary words. It efficiently conveys the tool's purpose without extraneous information.
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?
While the description is adequate for a simple list operation, it lacks details about the return format, how the 'current gallery album' is determined, and any constraints. For a tool with no output schema, more context would be beneficial.
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?
The tool has zero parameters with 100% schema coverage. The description implies no further input is needed, which matches the empty schema. It adds no confusion and is sufficient given no parameters exist.
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?
The description clearly states the tool lists stills in the current gallery album, using a specific verb and resource. It distinguishes from sibling tools like still_grab (capture), still_export (export), still_delete (delete), and still_albums (list albums).
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 provides no guidance on when to use this tool versus alternatives, such as still_albums. It does not specify prerequisites like requiring an open album or context for 'current gallery album'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/irstone-source/resolve-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server