Skip to main content
Glama

Follow-up messages and their timing

dosai_list_followup_steps
Read-onlyIdempotent

The follow-up chain: what the bot writes to a client who went silent, after how many hours, and whether each step is on. Official WhatsApp: wa_template_after_window=true means a client silent over 24 hours gets a paid template (wa_template_id, empty = the «bring the conversation back» template), false = the step is counted without a message. Use the ids to change a step.

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>"
    },
    "name": "dosai_list_followup_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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)$"
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description is free to spend its words on domain semantics, which it does well: it explains that wa_template_after_window=true sends a paid template after 24 hours of silence, false counts the step without messaging, and an empty wa_template_id means the default 'bring the conversation back' template. That is genuine behavioral disclosure about what each configuration value actually does, not restatement. Pagination and ordering are unmentioned, keeping it below a 5.

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?

Front-loaded with the resource definition, then immediately pivots to the WhatsApp template semantics, and closes with the ids-to-change routing. The middle clause is dense and reads as a run-on, but every sentence carries information an agent could not get from the schema or annotations.

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?

With no output schema, the description carries the burden of explaining return values; it covers the meaningful flags (wa_template_after_window, wa_template_id) but leaves the rest of the step shape — the hours/delay field and the step identifier fields — only implied. Adequate for a small configuration list, but the returned structure is not fully specified.

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?

There is a single required parameter, project_id, and the schema already documents it at 100% coverage ('From dosai_list_projects'). The description adds no additional meaning about the parameter, so the baseline 3 for a fully documented single-param schema applies.

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?

Describes the resource concretely: 'The follow-up chain: what the bot writes to a client who went silent, after how many hours, and whether each step is on' tells an agent exactly what comes back. It does not, however, distinguish this from dosai_list_followups or dosai_get_followup_status, nor does it use an explicit list verb.

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?

'Use the ids to change a step' gives a clear follow-on path to the update/delete siblings, which is a real routing signal. It stops short of stating when to choose this over dosai_list_followups or dosai_get_followup_status, so the agent must infer selection from the names alone.

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