Skip to main content
Glama

Change a follow-up step

dosai_update_followup_step
Destructive

Change one follow-up step: its text, the pause before it, a clock time, or switch it off. message_type: static = sent exactly as written, ai = the bot writes it from the conversation, ai_with_context = the bot writes it guided by message_text. Follow-ups reach real clients, confirm the text with the owner. 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>",
      "step_id": "<step_id>"
    },
    "name": "dosai_update_followup_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
step_idYesStep id from dosai_list_followup_steps.
after_24hNoOfficial WhatsApp, client silent over 24h: "reengage" (paid «bring back» template), an automation_templates id from dosai_get_whatsapp_template_settings, or "none" (step counted, nothing sent). One template per step. Paid: ask the owner.
is_activeNo
project_idYesFrom dosai_list_projects.
delay_hoursNoHours after the previous message.
message_textNo
message_typeNo
send_at_timeNoSend at this clock time (project time zone), or null to send by the pause only.
stop_on_replyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / after_24h
      Added value: +{
      +  "anyOf": [
      +    {
      +      "const": "reengage",
      +      "type": "string"
      +    },
      +    {
      +      "const": "none",
      +      "type": "string"
      +    },
      +    {
      +      "format": "uuid",
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Official WhatsApp, client silent over 24h: \"reengage\" (paid «bring back» template), an automation_templates id from dosai_get_whatsapp_template_settings, or \"none\" (step counted, nothing sent). One template per step. Paid: ask the owner."
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / message_type / enum
      Previous value: -[
      -  "static",
      -  "ai",
      -  "ai_with_context"
      -]New value: +[
      +  "ai",
      +  "static",
      +  "ai_with_context"
      +]
  3. 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."
  4. Changed2 schema fields changed
    • 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)$"
    • removedInput schema / properties / step_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)$"
  5. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds genuinely new behavioral facts: the edits affect live client messaging, the owner should confirm the text, and an editor role is required. It does not clarify partial-update semantics (which untouched fields survive) or how the deactivation affects in-flight steps, leaving some mutation behavior opaque.

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?

Four short sentences, each front-loaded and purposeful, with the most consequential caution (real clients) placed before minor detail. The message_type sentence is dense but earns its space because that enum is otherwise opaque. No filler or 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 9-parameter destructive mutation with no output schema, the definition covers role requirements, real-world blast radius, and the most confusing enum adequately. The remaining gaps (partial-update semantics, undocumented stop_on_reply/message_text behavior) are modest but real.

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

Parameters4/5

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

Schema coverage is only 56%, so the description must carry weight, and it does: it defines the three message_type values in plain terms and maps the prose facets ('the pause before it', 'a clock time', 'switch it off') onto delay_hours, send_at_time, and is_active. Parameters like stop_on_reply and message_text length limits remain undocumented in both places, which caps the score.

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 one follow-up step') and enumerates the editable facets: text, pause, clock time, or deactivation. That lets an agent separate it from dosai_add_followup_step and dosai_delete_followup_step by scope. It stops short of explicitly naming sibling alternatives, so a 4 rather than a 5.

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?

It supplies real prerequisites ('Requires editor role') and a strong operational caution ('Follow-ups reach real clients, confirm the text with the owner'), which steers usage. However, there is no explicit statement of when to prefer add/delete/list siblings, or which conditions make this tool inappropriate, so guidance is implied rather than spelled out.

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