Skip to main content
Glama

Create a scheduled report

dosai_create_report

A new report by schedule: leads, dialogs, money for the period, to email (the project's notification email, dosai_set_notify_email) or Telegram (the reports bot: dosai_connect_owner_telegram_bot with purpose=reports). Up to 10 per project. Change it later with 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>",
      "name": "<name>",
      "frequency": "<frequency>",
      "send_times": "<send_times>",
      "channels": "<channels>"
    },
    "name": "dosai_create_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
enabledNoDefault true.
channelsYes
frequencyYes
project_idYesFrom dosai_list_projects.
send_timesYesClock 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. 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.0
Behavior4/5

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

Annotations only declare a non-read-only, closed-world, non-destructive write, so the description must carry the rest — and it does: owner-only authorization, a hard quota of 10 per project, and per-channel setup dependencies that will make creation fail if unmet. It does not say whether an id is returned or how invalid timezones/weekdays are rejected, which keeps it out of 5 territory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every clause carries information, but it is delivered as one long fragment dense with nested parentheses, which makes it slower to parse than a short sentence per idea. No wasted words, but the structure is weak.

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 with no output schema, the description covers the things that actually cause failures: ownership, the 10-report cap, channel prerequisites, and where to go to modify the result. Only the return value and error behavior are unaddressed, which is minor given the schema handles field-level detail.

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 description coverage is 63%, and the description adds genuine meaning for the `channels` enum by tying each value to its required precondition (notify email vs. reports bot). The remaining parameters (name, frequency, send_times, send_weekdays, send_day_of_month, enabled) are left entirely to the schema, so this matches the baseline rather than exceeding it.

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 ('A new report by schedule') plus the content it covers (leads, dialogs, money for the period) and its delivery targets. An agent can distinguish this from dosai_update_report and dosai_send_report_now without opening any schema.

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 usage context: prerequisites per channel (dosai_set_notify_email for email, dosai_connect_owner_telegram_bot with purpose=reports for Telegram), the 'Up to 10 per project' cap, and an explicit redirect to dosai_update_report for later changes. It stops short of naming when to prefer dosai_send_report_now or dosai_set_daily_report instead, so it is not a full 5.

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