Skip to main content
Glama

Change a scheduled report

dosai_update_report
Destructive

Switch a report on or off and change when and where it goes. Only the fields you pass change, the rest stays as it is. Email reports go to the project's notification email (dosai_set_notify_email); Telegram needs the reports bot (dosai_connect_owner_telegram_bot with purpose=reports). Report ids: dosai_list_report_settings. 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>",
      "report_id": "<report_id>"
    },
    "name": "dosai_update_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo
channelsNo
frequencyNo
report_idYes
project_idYesFrom dosai_list_projects.
send_timesNoClock times in the project's time zone.
send_weekdaysNoFor weekly: 1 = Monday ... 7 = Sunday.
send_day_of_monthNoFor monthly.

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. Changed2 schema fields 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)$"
    • removedInput schema / properties / report_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?

Adds real context beyond the annotations: it discloses partial-update semantics ('Only the fields you pass change, the rest stays as it is'), which materially softens the destructiveHint=true flag, plus the owner-only permission requirement and per-channel prerequisites. It does not explain what is lost when channels are replaced or how validation failures surface, leaving some behavior unstated.

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 tight sentences, front-loaded with the core action, followed by the mutation semantics and then the setup prerequisites. The parenthetical sibling references are dense but each carries actionable information, and there is no 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 an 8-parameter mutation tool with no output schema and a destructive hint, this covers the important ground: partial-update behavior, id sourcing, channel prerequisites, and authorization. The remaining gap is error/validation behavior and the interaction between weekly and monthly scheduling fields, which the schema only partially handles.

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 only 50%, but the description compensates by mapping meaning onto the undocumented fields: 'switch on or off' for enabled, 'when' for frequency and send times, and 'where it goes' for channels, including the concrete email/Telegram delivery requirements. It still does not clarify how send_weekdays vs. send_day_of_month interact or how channel arrays are replaced.

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 specific verb and resource ('Switch a report on or off and change when and where it goes'), which covers both the enabled toggle and the scheduling/channel fields. It is clearly distinguishable from siblings like dosai_create_report, dosai_delete_report, and dosai_send_report_now, which do different things to a report.

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 concrete preconditions and routing: get report ids from dosai_list_report_settings, email requires dosai_set_notify_email, Telegram requires dosai_connect_owner_telegram_bot with purpose=reports, and it is owner-only. It does not explicitly say when to prefer a different tool (e.g. create vs. update vs. delete), so it stops short of full when/when-not guidance.

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