Skip to main content
Glama

DreamAgent

by io.github.nivethaug

dreamagent_cancel_chat

Destructive

DESTRUCTIVE — stops an AI edit that is currently running. Use ONLY when the user explicitly asks to stop/cancel the active edit. After cancellation, do NOT claim the requested change was completed — report that it was stopped.

Returns 'Cancellation requested: ' — e.g. 'Query cancelled', 'Cancellation requested' (durable run), or 'No active query found'. Afterwards poll dreamagent_get_chat_status / dreamagent_get_edit_progress until run_status reports 'cancelled'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_keyYesthe session key of the running edit.

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.6/5.0
Behavior5/5

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

Annotations already indicate destructiveHint=true, and the description reinforces this with 'DESTRUCTIVE —' and adds critical context: do not claim completion, report that it was stopped. It also discloses return value variations and the need to poll for final status.

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

Conciseness4/5

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

The description is compact yet packed with necessary information: warning, usage restriction, post-action behavior, return examples, and follow-up steps. Each sentence serves a purpose, though the density is slightly high.

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?

For a one-parameter destructive tool with a clear output schema, the description covers purpose, when to use, behavior after cancellation, possible return values, and follow-up polling. It is fully sufficient for an agent to invoke and handle the tool correctly.

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 covers session_key with 100% description coverage, so the baseline is 3. The description only refers to 'the running edit' without adding new parameter-level semantics beyond what the schema already provides.

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 'stops an AI edit that is currently running' with a specific verb and resource. It differentiates from sibling status-polling tools by focusing on cancellation, making it unambiguous.

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 'Use ONLY when the user explicitly asks to stop/cancel the active edit' and provides post-cancellation instructions, including naming sibling tools for polling (dreamagent_get_chat_status / 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