Skip to main content
Glama

Change a dialog

dosai_update_conversation
Destructive

Change a dialog: status (open | resolved | closed), tags (replaces the whole list), client name, archive, pin, or snooze until a date. Requires editor role.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "conversation_id": "<conversation_id>"
    },
    "name": "dosai_update_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoThe full new list of tags.
pinnedNo
statusNo
archivedNotrue = move to archive, false = bring back.
project_idYesFrom dosai_list_projects.
client_nameNo
snoozed_untilNoFuture ISO date to hide the dialog until, or null to clear.
conversation_idYesFrom dosai_list_conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / conversation_id / description
      Previous value: -"Conversation id, as returned by dosai_list_conversations."New value: +"From dosai_list_conversations."
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  3. Changed2 schema fields changed
    • removedInput schema / properties / conversation_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  4. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, destructive, closed-world mutation, so the bar is lower — and the description still adds genuine context: it discloses the authorization requirement (editor role) and the replacement semantics of tags ("replaces the whole list"), which the annotations cannot express. It stops short of saying whether unspecified fields are left untouched or how destructive an archive is, leaving some mutation behavior unstated.

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?

Two sentences, no filler: the field enumeration is front-loaded and the authorization requirement is appended as a short constraint. Every clause carries information an agent would otherwise have to infer.

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

Completeness3/5

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

For an 8-parameter destructive mutation with no output schema, the definition covers fields and auth but omits partial-update semantics (are unmentioned fields preserved?), any conflict or validation behavior, and what a successful call returns or whether it is reversible. Adequate to invoke, but an agent could act more confidently with those behaviors stated.

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 coverage is 63%, and most of the description's parameter detail duplicates what the schema already says — the status enum values, tags as a full replacement list, and archive true/false meaning are all present in property descriptions. It adds only light framing ("snooze until a date") and says nothing about the two required identifiers, so it neither compensates for the coverage gap nor contributes meaningfully beyond the schema.

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

Purpose4/5

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

The description opens with a specific verb and resource ("Change a dialog") and enumerates the mutable fields — status, tags, client name, archive, pin, snooze — so an agent knows exactly what surface this tool touches. It does not name a sibling to distinguish itself from, but the enumerated field set makes its scope unambiguous against neighbors like dosai_assign_conversation or dosai_clear_conversation.

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

Usage Guidelines3/5

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

The one explicit usage constraint is "Requires editor role," which is a real prerequisite an agent must check. There is no statement of when to prefer this tool over siblings (e.g., clearing vs. archiving a dialog) or any exclusion, so guidance is implied by the field list rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources