Skip to main content
Glama

Remind me about a lead

dosai_add_lead_reminder

Set a reminder on a lead, e.g. "call back tomorrow at 10". The team is notified in the cabinet. 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>",
      "lead_id": "<lead_id>",
      "due_at": "<due_at>"
    },
    "name": "dosai_add_lead_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
due_atYesISO 8601 date and time with the UTC offset of the project's time zone (see dosai_get_bot_settings.timezone), e.g. 2026-10-01T10:00:00Z for UTC.
lead_idYesFrom dosai_list_leads.
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lead_id / description
      Previous value: -"Lead id, as returned by dosai_list_leads."New value: +"From dosai_list_leads."
  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 / lead_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

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, so the bar is lower. The description adds real context beyond them: the team is notified in the cabinet and editor role is required. It leaves out what happens at due time, whether duplicates are allowed, or how to cancel, which matters for a reminder tool.

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?

Two short sentences, front-loaded with the action before the example and the permission requirement. Nothing is redundant, though the example is quoted without saying it maps to the note field.

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?

For a simple mutation with no output schema, the definition covers the action, an example, a side effect, and the role gate. It omits what the tool returns, timing semantics of due_at, and any pointer to listing/cancelling reminders, leaving moderate gaps.

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?

Schema coverage is 75%, with due_at fully specified including timezone and format, and lead_id/project_id pointing to their source list tools. Only note is undocumented, and the description's example hints at its content but adds no explicit constraint. Baseline 3 is appropriate.

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?

States a specific verb and resource ("Set a reminder on a lead") and illustrates the intent with a concrete example. It does not distinguish itself from the close sibling dosai_add_lead_notification, which an agent must choose against.

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?

The example "call back tomorrow at 10" implies the natural-language use case, and "Requires editor role" sets a precondition. There is no explicit when-not guidance and no named alternative (e.g. notification vs. reminder vs. followup step).

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