Skip to main content
Glama

DreamAgent

by io.github.nivethaug

dreamagent_get_project_status

Read-only

Check a project's creation/deployment state. Terminal states are 'ready' (built and live) and 'failed'; while a project is being created it reports progressive phases such as 'creating', 'building', 'deploying', or 'ai_provisioning' — treat any non-terminal status as still building. Use after dreamagent_create_project (poll until ready or failed) and whenever the user asks whether a project is ready or live.

NOTE: this reports the PROJECT's build/deploy state — NOT AI edit progress. For edits use dreamagent_get_edit_progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesthe project to check.

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

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description explains terminal states ('ready', 'failed'), progressive phases ('creating', 'building', 'deploying', 'ai_provisioning'), and instructs treating non-terminal states as still building. This adds meaningful interpretative context.

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 well-structured with a clear first sentence, followed by state details and usage guidance. The NOTE is valuable and not redundant. Every sentence earns its place with no fluff.

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 tool's simplicity (one param, output schema present, annotations provided), the description fully covers purpose, usage, state interpretation, and exclusions. No critical gaps remain.

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

Parameters3/5

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

Schema description coverage is 100% because project_id has a description ('the project to check'). The tool description adds no extra semantic value about the parameter, so baseline 3 is appropriate.

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 clearly states the tool checks a project's creation/deployment state, with a specific verb and resource. It explicitly distinguishes from sibling tools by noting it reports build/deploy state, not AI edit progress, and names the alternative tool for edits.

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?

Explicitly states when to use: after dreamagent_create_project (poll until ready or failed) and whenever the user asks if a project is ready or live. It also gives an exclusion by directing edit-progress queries to dreamagent_get_edit_progress.

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