Skip to main content
Glama

Add a follow-up step

dosai_add_followup_step

Add a step to the end of the follow-up chain (at most 10 steps). message_type: static = exactly this text, ai = the bot writes it itself, ai_with_context = the bot writes it guided by message_text. Confirm the text and timing 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>",
      "message_type": "<message_type>",
      "delay_hours": "<delay_hours>"
    },
    "name": "dosai_add_followup_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
project_idYesFrom dosai_list_projects.
delay_hoursYesHours after the previous message.
message_textNo
message_typeYes
send_at_timeNoSend at this clock time (project time zone).

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. Changed1 schema field 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)$"
  5. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, non-open-world; the description adds the 10-step ceiling, the editor-role authorization requirement, and an owner-confirmation step — all behavior an agent cannot infer from annotations. It stops short of describing what the call returns or how ordering/delays cascade to later steps.

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?

Four compact sentences, front-loaded with the action and its cap, then semantics, then prerequisites. 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 6-parameter mutation tool with no output schema, the description covers the cap, authorization, and the ambiguity-prone enum, which is most of what an agent needs. Missing only error/return behavior and the interaction between new steps and existing chain timing.

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 67%, and the description compensates by defining the three message_type values precisely (static = fixed text, ai = bot writes freely, ai_with_context = bot writes guided by message_text), which the schema lists as a bare enum. It adds nothing for delay_hours, send_at_time, or after_24h, which are already described in the schema.

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?

States a specific verb and resource ('Add a step to the end of the follow-up chain') and adds the positional constraint that the step appends rather than modifies or inserts, which separates it from dosai_update_followup_step and dosai_delete_followup_step.

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 concrete precondition ('Requires editor role') and a workflow instruction ('Confirm the text and timing with the owner'), plus the hard cap of 10 steps that tells the agent when the tool will fail. It does not explicitly name the update/delete siblings as alternatives, so it falls short of a 5.

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