A model handed eleven tools will pick one that looks relevant and skip the one that would have told it how to phrase the request. Dreamlit writes the ordering into the descriptions — read the guidance, find the project, then create the draft — which is the difference between a workflow that describes an outcome and one that describes a guess. Note that creation produces a draft rather than a live automation, which is the right default for something an agent wrote.
Dreamlit's endpoint, which listed 11 tools to our probe as Dreamlit MCP 0.3.0. The tool descriptions are written as instructions to the calling agent — get_status is marked as the first call for product and prompting guidance.
- get_status — read-only, and documented as the first call: product guidance, prompting guidance and approval state
- list_projects and list_workflows — find the project or workflow by name, description or trigger type when only a name is known
- create_or_update_workflow — create a draft, or update an existing one, from an outcome-oriented description
- And the rest of the eleven, covering inspection and the surrounding workflow state
The handshake answered without credentials; account-scoped operations are what the parameters imply.
Paste a URL — add the endpoint to your client