Skip to main content
Glama

Make the bot answer the client now

dosai_reply_now
Destructive

Have the bot answer the client's last unanswered message in a conversation right away (it came while the bot was off or silent there). enable=true first switches the bot on in this conversation, the same way the cabinet button does: the number also leaves the "bot never answers here" list and its spam and message-limit blocks are lifted. The answer is written by the bot from its prompt and knowledge and goes to the real client; it is charged like any bot answer. 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>"
    },
    "name": "dosai_reply_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
enableNotrue = switch the bot on in this conversation first.
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

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses concrete side effects: the number leaves the "bot never answers here" list, its spam and message-limit blocks are lifted, the reply goes to a real client, and it is billed like any bot answer. It also states the editor-role requirement. This is exactly the behavioral context annotations cannot carry.

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?

The core action is front-loaded in the first clause, followed by the enable semantics, effects, and billing and permission notes in a compact flow. Every sentence adds information the schema and annotations do not already provide.

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 three-parameter mutation with a 100% documented schema, no output schema, and destructive/openWorld annotations, the description supplies the missing pieces: cost, permission requirement, and irreversible side effects on the number's block lists. Nothing needed to invoke it correctly appears absent.

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 100%, so the baseline would be 3, but the description adds real meaning to enable=true — it mirrors the cabinet button, removes the number from the never-answer list, and clears spam and limit blocks. project_id and conversation_id remain schema-only, which is adequate given their UUID provenance hints.

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 states a specific verb and resource: make the bot answer the client's last unanswered message in a conversation, qualified by the condition that the message arrived while the bot was off or silent. That is far more precise than the title alone. It does not explicitly name a sibling such as dosai_toggle_bot_in_conversation or dosai_answer_bot_gap, so the distinction must be inferred from the wording.

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?

The trigger condition is stated clearly (the last unanswered message came while the bot was off or silent here), along with the effect of enable=true and the editor-role prerequisite. What is missing is explicit routing: it never says when to use dosai_toggle_bot_in_conversation or dosai_answer_bot_gap instead.

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