Skip to main content
Glama

Notify the owner about new leads

dosai_add_lead_notification

Make the bot tell the OWNER about a new lead with the client's name and phone: by email (works at once) or to a WhatsApp number or group (needs the project's WhatsApp connected; the message goes from the business number). The address must be the owner's or their team's, confirm it with the owner: every future lead's contact goes there. 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>",
      "via": "<via>",
      "to": "<to>"
    },
    "name": "dosai_add_lead_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEmail address, or a WhatsApp number like +77011234567.
viaYes
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

A4.4/5.0
Behavior4/5

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

Beyond the annotations (write, open-world, non-destructive), it discloses the crucial persistence trait: the address receives 'every future lead's contact', so this is durable config, not a one-off send. It also notes WhatsApp messages go out from the business number and that the project must be connected. Apart from not stating whether it adds a channel or replaces existing settings, the behavioral profile is well covered.

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?

Two sentences, front-loaded with the action and channels, then the address-choice caution and role requirement. Parentheticals carry load-bearing detail (immediacy, connection prerequisite, sender number) rather than filler.

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

Completeness4/5

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

For a 3-parameter mutation with no output schema, the definition covers prerequisites, permissions, persistence and address validation. The one meaningful gap is whether this appends a notification destination or overwrites existing ones, which matters given the sibling settings tools.

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 67% and the `via` enum carries no schema description, so the description must compensate; it does, explaining the email vs WhatsApp choice and the connection requirement behind WhatsApp. It also adds meaning to `to` by constraining it to the owner's or their team's address and telling the agent to confirm it with the owner. Number formatting is left to the schema.

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 concrete verb+resource+effect: make the bot tell the OWNER about a new lead, carrying the client's name and phone. The two delivery channels (email vs WhatsApp number/group) are spelled out, which is enough for an agent to distinguish this from settings-management siblings like dosai_set_notify_email or dosai_update_notification_settings.

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 real preconditions: email 'works at once' while WhatsApp 'needs the project's WhatsApp connected', and it requires editor role. It does not name alternatives (e.g. dosai_send_test_notification to verify, or the settings tools to inspect current config), so the agent must infer routing.

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