Skip to main content
Glama

Send the next follow-up without waiting

dosai_trigger_followup
Destructive

Send the next touch of a client's follow-up chain now instead of waiting for its delay (subscriber id: field id in dosai_list_followups). It goes with the next run of the sender, within minutes, past the step's pause, the step's clock time and "restart on reply"; a pause on this client is lifted. It still obeys the project's sending hours and the night ban, so outside them it waits for the window. Refused when the client unsubscribed, the chain is finished or cancelled, or the bot is off in that chat. The message goes to a real client. 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>",
      "subscriber_id": "<subscriber_id>"
    },
    "name": "dosai_trigger_followup"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
subscriber_idYes

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. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description goes beyond them by explaining what actually happens: it rides the next sender run (minutes), bypasses the step pause, clock time and restart-on-reply, and lifts an existing pause. It also warns 'The message goes to a real client' and names the required editor role. It does not describe the response shape, but that is a minor gap against otherwise strong disclosure.

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?

The triggering behavior is front-loaded in the first sentence, followed by timing mechanics and then refusal conditions in a logical order. Some sentences are densely packed with nested clauses ('past the step's pause, the step's clock time and "restart on reply"'), but no content is filler.

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

Completeness5/5

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

For a destructive, side-effecting trigger with no output schema, the description covers timing, precedence over step-level gating, legal/temporal constraints, failure modes, and permission requirements. An agent has enough to decide whether to call it and what to expect.

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 50%: project_id is documented in the schema while subscriber_id is not. The description compensates by stating the subscriber id is the id from dosai_list_followups, which is the disambiguation an agent actually needs. With only two parameters, that closes most of the semantic gap.

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?

The description states a specific verb and resource ('Send the next touch of a client's follow-up chain now instead of waiting for its delay') and immediately contrasts with the waiting/scheduled alternative. It also cross-references dosai_list_followups for the subscriber id, so an agent can distinguish it from the listing siblings without opening a schema.

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

Usage Guidelines5/5

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

It states exactly when to use it (to send immediately rather than wait out the delay) and enumerates when it will be refused: client unsubscribed, chain finished or cancelled, or bot off in that chat. It further clarifies interaction with sending hours and the night ban, which is the main 'it may not happen now after all' caveat an agent needs.

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