Skip to main content
Glama

Owner's email for notifications and reports

dosai_set_notify_email
Destructive

Set the email where the platform writes to the OWNER: reports, notifications about payments and new dialogs. Never a client's address. Empty string turns email notifications off. Requires admin or owner 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>",
      "email": "<email>"
    },
    "name": "dosai_set_notify_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes
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.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds real value on top: it discloses the authorization requirement (admin or owner role) and the concrete destructive effect (empty string turns notifications off). It does not describe what happens to previously configured values or whether the change is reversible, which is the remaining gap for a destructive mutation.

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?

Three short sentences, front-loaded with the core action, then the scope warning, then the off-switch and permission requirement. No filler and no repetition of the title.

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 two-parameter mutation with no output schema, the description covers purpose, scope, the disabling value, and the required role. An agent has everything needed to decide to call it and to construct a valid call.

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 50%: project_id is documented in-schema ('From dosai_list_projects') while email carries only format/pattern constraints. The description compensates by explaining that email is the owner's address and that the empty string is a valid disabling value, which is meaningful beyond the schema. Baseline 3 is appropriate given the schema already handles the project_id reference.

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 the email where the platform writes to the OWNER') and enumerates the message classes it governs: reports, payment notifications, new dialogs. It also draws a hard scope boundary ('Never a client's address'), which prevents confusion with lead/contact email fields. It stops short of naming a sibling such as the owner Telegram-connection tools, so it is clear but not sibling-differentiated.

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 (owner-facing reports and notifications) and an explicit off-switch: an empty string disables email notifications. It also states the prerequisite role (admin or owner). It does not mention alternative channels for owner notifications, but the when-to-use condition itself is unambiguous.

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