Skip to main content
Glama

Take clients off the "not delivered" list

dosai_restore_undelivered
Destructive

Clear the "not delivered" mark for the given conversations (ids: dosai_list_undelivered, up to 50), so broadcasts and operator messages reach them again. Nothing is sent by this call. A follow-up chain that the mark cancelled becomes active again and continues from its next step after that step's pause (not if AI is off in the chat or the lead was handed to the owner; a client silent beyond the project's silence limit is closed by the engine as usual). The same happens by itself when the client writes. A contact marked blocked is also taken off the "do not write" list of cold outreach. The mark returns only if a NEW message to that person hangs undelivered too. 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_ids": "<conversation_ids>"
    },
    "name": "dosai_restore_undelivered"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
conversation_idsYes

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. Changed2 schema fields changed
    • removedInput schema / properties / conversation_ids / items / 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)$"
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: nothing is sent, a cancelled follow-up chain reactivates and resumes after its pause step, with named exceptions (AI off, lead handed to owner, silence limit) and a side effect on blocked contacts (removed from the cold-outreach do-not-write list). The editor-role requirement and the condition under which the mark reappears are also disclosed.

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 core action and the "Nothing is sent" caveat early; every sentence carries operational information. The long nested parenthetical about reactivation conditions is dense and slightly harder to parse than necessary.

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 state-changing tool with no output schema, the description covers side effects, prerequisites (editor role), reactivation exceptions, and the condition under which the mark returns. Nothing material an agent needs before invoking it is missing.

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%, with conversation_ids undocumented in the schema; the description compensates by naming dosai_list_undelivered as the source of those ids. The "up to 50" limit merely repeats the schema's maxItems, and project_id gets no added explanation beyond the schema's own pointer.

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 ("Clear the 'not delivered' mark for the given conversations") and explicitly points at the sibling that supplies the inputs (dosai_list_undelivered). An agent can distinguish this from the list tool without opening either schema.

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 clear context for use (re-enabling delivery of broadcasts and operator messages) and notes that the mark clears automatically when the client writes, implicitly signaling when no call is needed. It stops short of an explicit when-not-to-use rule, and its single sibling reference is only a data source, not an alternative action.

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