Skip to main content
Glama

Schedule a message to a client

dosai_schedule_message
Destructive

Queue a message that will reach a REAL client later (from a minute to a month ahead). Once sent it cannot be unsent, so confirm the wording and time with the user before calling. 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>",
      "text": "<text>",
      "send_at": "<send_at>"
    },
    "name": "dosai_schedule_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesExactly what the client will see.
send_atYesISO 8601 date and time with the UTC offset of the project's time zone (see dosai_get_bot_settings.timezone), e.g. 2026-10-01T10:00:00Z for UTC.
project_idYesFrom dosai_list_projects.
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.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the irreversibility and external-reach concepts are partly structured. The description still adds real value with 'Once sent it cannot be unsent' and the 'Requires editor role' authorization requirement, which annotations do not convey; however it says nothing about failure modes, delivery confirmation, or whether a queued message remains editable before dispatch.

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?

Three short sentences, front-loaded with the core action, then the risk warning, then the permission prerequisite. No filler or redundant restatement of the title.

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

Completeness4/5

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

For a destructive, externally visible mutation with no output schema, the description covers the audience, the timing window, the irreversibility, and the role requirement — enough to call it correctly and cautiously. It lacks only post-call information such as the returned schedule identifier or how to reference the queued message for later cancellation or editing.

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 100%, so the schema already explains all four parameters, including the ISO 8601 offset requirement for send_at. The description's only parameter-relevant contribution is the one-minute-to-one-month window, which constrains send_at meaningfully but is a single extra fact rather than substantive semantics 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?

States a specific verb (queue/schedule) and resource (a message to a client) and adds the qualifier 'REAL client' plus the delivery window 'from a minute to a month ahead', which distinguishes it from an immediate-send tool. It stops short of naming the immediate-send or cancel siblings, so the differentiation is inferential rather than explicit.

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

Usage Guidelines4/5

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

Gives a clear usage envelope (delayed delivery between one minute and one month) and a procedural precondition ('confirm the wording and time with the user before calling'), plus the editor-role requirement. It does not say when NOT to use it, e.g. that an immediate send should go through a different tool or that a queued message is retractable via the cancel sibling.

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