Skip to main content
Glama

DreamAgent

by io.github.nivethaug

dreamagent_create_project

WRITE ACTION — creates a new DreamAgent project (website, Telegram bot, Discord bot, or scheduler). Use ONLY when the user clearly asks to create/build a new project; not for questions about what to build.

CONFIRM BEFORE CALLING — never create on the first mention. In ONE message, present and get the user's explicit go-ahead for:

  1. The credential: run dreamagent_list_global_integrations first. If several telegram/discord credentials are saved, list them (id + title) and ask which to use. If exactly one is saved, state which one you will use. Never pick silently.

  2. The plan: name, type, and the final description exactly as you will submit it (this is the Prompt Assistant's recommendation summary). Call this tool only after the user confirms.

CREATION IS ASYNCHRONOUS: after calling, check dreamagent_get_project_status repeatedly until the project is 'ready' or 'failed' (bots ~2-5 min, websites longer).

CREDENTIALS: raw bot tokens are never accepted in chat or as inputs. For Telegram/Discord bots you MUST pass bot_token_integration_id — the ID of a saved credential from dreamagent_list_global_integrations. If none is saved, direct the user to dreamagent.cloud → Settings → Global Integrations. Other saved keys can be imported via global_integration_ids. Credentials are stored as project secrets and are never exposed back.

DESCRIPTION = the refined creation brief. Act as a Creative Director / Product Manager, not an architect.

Create a concise but complete description of WHAT should be built:

  • product vision and target audience

  • user experience and core functionality

  • design/tone direction

  • important features and behavior

  • final expected result

Do not include implementation details such as:

  • technology stack

  • architecture

  • database/API implementation

  • authentication implementation

  • deployment

  • CI/CD

  • testing commands

Infer reasonable defaults when missing details are non-critical. Ask for clarification only when missing information materially affects the requested functionality, scope, credentials, or expected result.

Prefer the following structure and constraints for each project type, but do not override explicit user requirements:

Website:

  • Project Vision

  • Design Style

  • Pages

  • Hero Experience

  • Core Features

  • UI Components

  • Mobile Experience

  • Final Expectation

  • Prefer up to 4 pages unless the user clearly requires more.

Telegram bot:

  • Bot Purpose

  • Commands

  • User Flow

  • Optional AI Features

  • Integrations when required

  • Final Expectations

  • Prefer a compact command set; always include /start and /help unless the user's explicit requirements conflict.

Discord bot:

  • Bot Purpose

  • Slash Commands

  • Events

  • Permissions

  • Optional AI Features

  • Final Expectations

  • Prefer a compact command set; include /help where appropriate.

Scheduler:

  • Job Purpose

  • Data Sources

  • Schedule

  • Delivery Channels

  • Message Format

  • Final Expectations

  • Use concrete schedules and specify failure/timeout behavior.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesproject name (max 30 chars; a public subdomain is auto-generated).
env_varsNooptional non-secret environment variables.
descriptionNothe build request (what + for whom + features/tone).
project_typeYeswebsite / telegrambot / discordbot / scheduler.
global_integration_idsNooptional saved-key IDs to import as env vars.
bot_token_integration_idNoREQUIRED for telegrambot & discordbot — saved-credential ID (see dreamagent_list_global_integrations).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description reveals critical behavioral traits: creation is asynchronous, raw bot tokens are never accepted, credentials are stored as secrets and never exposed, and it 'never create[s] on the first mention.' This gives the agent a complete safety and workflow model with no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but the complexity justifies it: 6 parameters, 4 project types, and critical safeguards. It is well-structured with bold section headers, bullet lists for each project type, and front-loaded key warnings like 'WRITE ACTION' and 'CONFIRM BEFORE CALLING.' Every section carries necessary information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and the tool's complexity, the description covers all operational context: pre-call credential discovery, confirmation steps, asynchronous behavior with status polling, default-inference guidance, and per-type description templates. The agent has everything needed to invoke the tool correctly without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already covers 100% of parameters, the description adds deep semantics: bot_token_integration_id is REQUIRED for Telegram/Discord bots and must come from dreamagent_list_global_integrations, description is a creative brief with explicit inclusions/exclusions, and global_integration_ids imports saved keys. It transforms bare parameter names into actionable guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'WRITE ACTION — creates a new DreamAgent project' and enumerates the four project types, giving a specific verb, resource, and scope. It also distinguishes itself from siblings by explicitly stating 'not for questions about what to build' and later referencing dreamagent_get_project_status for the asynchronous follow-up.

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

Usage Guidelines5/5

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

Provides explicit when-to-use: 'Use ONLY when the user clearly asks to create/build a new project; not for questions about what to build.' It goes further with a mandatory confirmation protocol, steps to list/choose integrations, and the instruction to poll dreamagent_get_project_status after calling, making alternatives and sequencing unmistakable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DreamAgent toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: project creation, listing, status checks, edit progress, session management, and integration queries. The status tools (get_chat_status, get_edit_progress, get_project_status) are carefully differentiated by their input and purpose, so there is no real ambiguity.

Naming Consistency5/5

All tool names follow a consistent pattern of 'dreamagent_' plus a verb_noun structure (e.g., create_project, list_sessions, get_edit_progress). This makes the entire set predictable and easy to navigate.

Tool Count5/5

With 12 tools, the set is well-scoped for managing DreamAgent projects and edits. Each tool covers a necessary operation without redundancy or bloat, staying comfortably within the ideal range.

Completeness4/5

The tool set comprehensively covers project creation, listing, status monitoring, AI editing, session management, and integration inspection. The notable gap is the lack of an update or delete project operation, but the core lifecycle and editing workflows are well covered.

Resources