@dreamlayer/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DREAMLAYER_API_KEY | Yes | Your DreamLayer API key (must be set in the server's own environment, e.g., dlr_live_your_key) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dreamlayer_capabilitiesA | Inspect the DreamLayer Agent API contract and the operations this key may run. Calls no provider and spends nothing. |
| dreamlayer_upload_imageA | Upload one local image for use as a reference. Returns an input_asset_id to pass to dreamlayer_generate. |
| dreamlayer_generateA | Generate or edit an image and return the resulting event stream. May end asking the user a question instead of producing an image; that is not a failure. Costs one credit per finished image. |
| dreamlayer_executionA | Read canonical state for one execution. Use this after any uncertain response. |
| dreamlayer_eventsC | Resume an execution's events after a drop. Pass the last event id you actually processed. |
| dreamlayer_cancelB | Request cancellation of an execution before it dispatches. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct phase in the image generation workflow: capabilities, upload, generate, execution status, event resumption, and cancellation. No two tools overlap in purpose, so an agent can reliably select the correct one.
All tools share the 'dreamlayer_' prefix, but the action words mix verbs (upload, generate, cancel) and nouns (capabilities, execution, events). The pattern is still predictable and readable, with only minor stylistic inconsistency.
With 6 tools, the surface is well-scoped for an image generation API. Each tool serves a necessary function, and the count feels neither sparse nor bloated.
The set covers the full lifecycle: capability introspection, asset upload, generation, status retrieval, event continuation, and cancellation. No obvious gaps exist for the domain, and all actions lead to resolvable outcomes.