Skip to main content
Glama

Switch the daily report on or off

dosai_set_daily_report
Destructive

The simplest report: once a day the owner gets how many clients wrote, how many leads and what was spent, in the same Telegram and email as the other notifications (link them first). Fine tuning (time, weekly, own content): dosai_update_report. Owner 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>",
      "enabled": "<enabled>"
    },
    "name": "dosai_set_daily_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
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

A3.6/5.0
Behavior3/5

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

The description adds real context beyond annotations: 'link them first' flags a required Telegram/email linkage before the report can be delivered, and 'Owner only' states an authorization constraint. However, annotations declare destructiveHint=true, and the description never explains what 'off' actually destroys or preserves (delivery only vs. stored settings) — that is the one behavior an agent most needs disclosed here.

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?

One tightly packed sentence with a parenthetical prerequisite, alternative, and permission note, with the report contents front-loaded. Dense but every clause carries information; minor cost is that the toggle verb itself is buried.

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 2-parameter toggle with no output schema and annotations covering the safety profile, the description supplies prerequisites, permissions, and the sibling to use for configuration. Only the effect of disabling remains unspecified, which for a destructiveHint-flagged tool is a small but real gap.

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 already carries its source ('From dosai_list_projects'). The description does not mention `enabled` directly, but the surrounding text makes the on/off semantics of that boolean unambiguous, so it compensates adequately without adding format detail.

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?

The description names the resource (the daily report) and its payload (clients who wrote, leads, spend), and the sibling dosai_update_report is explicitly excluded from scope. The actual toggle action is only implicit — carried by 'The simplest report' plus the title and the required `enabled` flag — so it is clear but one step short of an explicit verb.

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?

'Fine tuning (time, weekly, own content): dosai_update_report' routes the agent to the correct alternative for configuration changes, and 'Owner only' sets a caller prerequisite. There is no explicit statement of when not to use it (e.g. use dosai_send_report_now to trigger a one-off delivery), but the primary fork is covered.

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