Skip to main content
Glama

Where the owner's notifications go

dosai_get_notification_settings
Read-onlyIdempotent

Where and about what the platform notifies the OWNER: email, WhatsApp number, whether a Telegram chat is linked, and which events are switched on. Low balance, bot errors and a disconnected channel always arrive and are not in the list. How Telegram is linked: dosai_get_owner_telegram. Addresses are visible to the owner and admins only.

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>"
    },
    "name": "dosai_get_notification_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses that low balance, bot errors, and disconnected-channel alerts always arrive and are excluded from the returned event list. It also adds an access restriction: addresses are visible only to the owner and admins.

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 description is compact and front-loaded, starting with the core purpose and then adding important exceptions, the Telegram alternative, and visibility limits. Every sentence contributes useful information without repetition.

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 one-parameter read-only settings tool with no output schema, the definition is complete enough to invoke correctly. It covers what is returned, what is always excluded, where to find Telegram linkage, and who can see addresses.

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 100% for the single required project_id parameter, so the schema already documents its meaning and source. The description does not add further semantics about project_id, so the baseline score is appropriate.

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?

The description states a specific resource and scope: it returns where and about what the platform notifies the OWNER, including email, WhatsApp, Telegram linkage, and enabled events. It clearly distinguishes this read operation from configuration or Telegram-linking details.

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 description gives clear context for when to retrieve notification settings and explicitly routes Telegram-linking details to dosai_get_owner_telegram. It does not explicitly contrast with dosai_update_notification_settings, but the read-only scope is clear.

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