get_presetRead one style in full — its reader-facing description and the prompt_fragment a provider receives.
| Name | Required | Description | Default |
|---|---|---|---|
| preset_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| preset | Yes | ||
| message | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / preset / properties / category / anyOfPrevious value: -[
- {
- "enum": [
- "photorealistic",
- "cinematic",
- "3d_animation",
- "cartoon",
- "anime"
- ],
- "type": "string"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "enum": [
+ "photorealistic",
+ "cinematic",
+ "3d_animation",
+ "cartoon",
+ "anime",
+ "pan_tilt",
+ "zoom_lens",
+ "dolly_track",
+ "slide_orbit",
+ "handheld_body",
+ "drone_crane",
+ "specials"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / preset / properties / compatibility / items / properties / model / enumPrevious value: -[
- "seedream-5-lite",
- "nano-banana-2.1",
- "nano-banana-2",
- "gpt-image-2.5-flare",
- "gpt-image-2.5-sunburst",
- "gpt-image-2",
- "nano-banana-2-lite",
- "seedream-5-pro",
- "seedream-5-pro-spicy",
- "flux-schnell",
- "flux-2-flex",
- "flux-2-pro",
- "flux-2-max",
- "recraft-v4.1-svg",
- "recraft-v4.1-pro-svg",
- "p-image",
- "grok-imagine-image",
- "grok-imagine-image-quality",
- "soul-2",
- "seedance-2.5",
- "seedance-2.5-spicy",
- "seedance-2.0",
- "seedance-2.0-mini",
- "seedance-2.0-fast",
- "grok-imagine-video-1.5",
- "veo-3.1",
- "veo-3.1-fast",
- "veo-3.1-lite",
- "gemini-omni-1.1",
- "kling-v3-omni-video",
- "kling-v3-video",
- "happyhorse-1.0",
- "wan-3",
- "wan-3-prime",
- "gen-4.5",
- "p-video",
- "p-video-2",
- "flux-3",
- "minimax-h3-max",
- "p-video-avatar",
- "p-video-animate",
- "p-video-replace",
- "omni-human-1.5",
- "kling-avatar-v2",
- "kling-v3-motion-control",
- "kling-lip-sync",
- "sync-lipsync-2",
- "genjutsu-motion-transfer",
- "genjutsu-object-swap",
- "grok-4.6",
- "gemini-3.8-flash",
- "gpt-6-luna",
- "elevenlabs-tts",
- "eleven-v4",
- "gemini-3.1-flash-tts",
- "kokoro-82m",
- "minimax-speech-2.8-hd",
- "inworld-tts-2",
- "reel-music-1",
- "minimax-music-2.6",
- "eleven-music"
-]New value: +[
+ "seedream-5-lite",
+ "nano-banana-2.1",
+ "nano-banana-2",
+ "gpt-image-2.5-flare",
+ "gpt-image-2.5-sunburst",
+ "gpt-image-2",
+ "nano-banana-2-lite",
+ "seedream-5-pro",
+ "seedream-5-pro-spicy",
+ "flux-schnell",
+ "flux-2-flex",
+ "flux-2-pro",
+ "flux-2-max",
+ "recraft-v4.1-svg",
+ "recraft-v4.1-pro-svg",
+ "p-image",
+ "grok-imagine-image",
+ "grok-imagine-image-quality",
+ "krea-3",
+ "qwen-image-3-pro",
+ "soul-2",
+ "seedance-2.5",
+ "seedance-2.5-spicy",
+ "seedance-2.0",
+ "seedance-2.0-mini",
+ "seedance-2.0-fast",
+ "grok-imagine-video-1.5",
+ "veo-3.1",
+ "veo-3.1-fast",
+ "veo-3.1-lite",
+ "gemini-omni-1.1",
+ "kling-v3-omni-video",
+ "kling-v3-video",
+ "happyhorse-1.0",
+ "wan-3",
+ "wan-3-prime",
+ "gen-4.5",
+ "p-video",
+ "p-video-2",
+ "flux-3",
+ "minimax-h3-max",
+ "p-video-avatar",
+ "p-video-animate",
+ "p-video-replace",
+ "omni-human-1.5",
+ "kling-avatar-v2",
+ "kling-v3-motion-control",
+ "kling-lip-sync",
+ "sync-lipsync-2",
+ "genjutsu-motion-transfer",
+ "genjutsu-object-swap",
+ "grok-4.6",
+ "gemini-3.8-flash",
+ "gpt-6-luna",
+ "elevenlabs-tts",
+ "eleven-v4",
+ "gemini-3.1-flash-tts",
+ "kokoro-82m",
+ "minimax-speech-2.8-hd",
+ "inworld-tts-2",
+ "reel-music-1",
+ "minimax-music-2.6",
+ "eleven-music"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare this as a safe, read-only, idempotent operation. The description adds useful semantic context about what 'full' means by naming the reader-facing description and provider prompt fragment, but it does not add behavioral details such as error handling, permissions, or rate limits.
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?
It is a single front-loaded sentence with no wasted words. The core operation and the returned fields are stated immediately.
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?
For a low-complexity read-only tool with rich annotations and an output schema, the description is largely complete. The main remaining gap is that it does not explain how to source the preset_id or explicitly route agents from list_presets to this tool.
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?
There is one parameter, `preset_id`, with 0% schema description coverage. The description does not identify the parameter, explain that it is a UUID, or say where to obtain it, so it does not compensate for the schema's lack of description.
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 uses a specific verb and resource: 'Read one style in full.' The word 'one' distinguishes it from the sibling list_presets, and it names the concrete fields returned (`description` and `prompt_fragment`), so an agent can identify the operation without opening the schema.
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 usage by stating it reads one style in full, which suggests fetching a known preset by ID rather than listing presets. However, it does not explicitly state when to use this versus list_presets, nor does it mention prerequisites or error conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.