Skip to main content
Glama

Schedule report

schedule_report
DestructiveIdempotent

Schedule one saved analysis to be emailed as a digest (CSV attached) to workspace members on a daily / weekly / monthly cadence (UTC); a dashboard cannot be scheduled — choose or save one panel as an analysis first. One schedule per report: calling again replaces every field, so re-pass conditions and recipients to keep them. day_of_week (0=Sun) applies weekly, day_of_month (1–28) monthly; recipients default to you. With conditions the digest sends only when ANY is met by that run's result, else that occurrence is skipped. Returns the schedule. List schedules with search_records(report_schedule); delete one with delete_record(report_schedule).

When to use: The user wants a saved analysis emailed on a schedule — 'email me this every Monday'.

Example: Email the pipeline report to the sales team every Monday at 8am.

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": {
      "report_id": "<report_id>",
      "frequency": "<frequency>"
    },
    "name": "schedule_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
hourNoHour of day to send, 0–23 in UTC (default 8).
enabledNoWhether the schedule is active (default true); pass false to keep the schedule but stop sending.
frequencyYesCadence of the digest: daily, weekly (with day_of_week) or monthly (with day_of_month); every run fires at `hour` UTC.
report_idYesThe saved analysis to schedule, by id (uuid); one schedule per report, so calling again replaces it. Dashboards and segments are refused.
conditionsNoUp to 5 {target, op, value} send conditions — target is "row_count" or an aggregation alias, op is gt|gte|lt|lte|eq|neq, value a number; omit to always send.
recipientsNoWorkspace member user ids (uuids) to email; defaults to just you, and any id that is not a member is refused.
day_of_weekNoWeekly only: day to send, 0=Sunday … 6=Saturday; defaults to Monday when omitted. Ignored for daily and monthly.
day_of_monthNoMonthly only: day to send, 1–28 (so every month has it); defaults to the 1st when omitted. Ignored for daily and weekly.

Output Schema

NameRequiredDescriptionDefault
scheduleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changed
    • removedInput schema / properties / recipients / items / 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. Changed17 schema fields changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / schedule / additionalProperties
      Removed value: -{}
    • changedOutput schema / properties / schedule / properties / conditions / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "additionalProperties": false,
      -      "properties": {
      -        "op": {
      -          "enum": [
      -            "gt",
      -            "gte",
      -            "lt",
      -            "lte",
      -            "eq",
      -            "neq"
      -          ],
      -          "type": "string"
      -        },
      -        "target": {
      -          "minLength": 1,
      -          "type": "string"
      -        },
      -        "value": {
      -          "type": "number"
      -        }
      -      },
      -      "required": [
      -        "target",
      -        "op",
      -        "value"
      -      ],
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "properties": {
      +        "op": {
      +          "enum": [
      +            "gt",
      +            "gte",
      +            "lt",
      +            "lte",
      +            "eq",
      +            "neq"
      +          ],
      +          "type": "string"
      +        },
      +        "target": {
      +          "minLength": 1,
      +          "type": "string"
      +        },
      +        "value": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "target",
      +        "op",
      +        "value"
      +      ],
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / schedule / properties / day_of_month / anyOf
      Removed value: -[
      -  {
      -    "maximum": 9007199254740991,
      -    "minimum": -9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / schedule / properties / day_of_month / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / schedule / properties / day_of_month / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / schedule / properties / day_of_month / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedOutput schema / properties / schedule / properties / day_of_week / anyOf
      Removed value: -[
      -  {
      -    "maximum": 9007199254740991,
      -    "minimum": -9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / schedule / properties / day_of_week / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / schedule / properties / day_of_week / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / schedule / properties / day_of_week / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedOutput schema / properties / schedule / properties / 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)$"
    • removedOutput schema / properties / schedule / properties / last_run_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / schedule / properties / last_run_at / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / schedule / 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)$"
    • removedOutput schema / properties / schedule / properties / workspace_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)$"
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, destructive and idempotent, and the description contributes real context beyond them: one schedule per report with full replacement semantics (re-pass conditions and recipients to keep them), UTC cadence, recipients defaulting to the caller, non-member ids refused, and conditional sends that skip the occurrence when no condition matches. It stops short of stating auth/permission requirements or failure modes, so it is strong but not exhaustive.

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?

Front-loaded with the core operation, then constraints, then alternatives, then a use-when line and example — a sound ordering. The middle paragraph is quite dense with semicolon-chained clauses, but each sentence carries distinct information, so little is wasted.

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 an 8-parameter mutation tool this is complete: the return value is covered by the output schema, the replace-on-recall semantics and conditional-send behavior are disclosed, the dashboard-instead-of-analysis prerequisite is called out, and the lifecycle (list/delete) is pointed at siblings.

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 100%, so the baseline is 3; the description still adds behavior the schema does not spell out, notably that conditions are ANY-of (not all) and that a failed condition skips that run rather than the schedule, plus the weekly/monthly applicability of day_of_week and day_of_month. It does not add syntax or format detail for hour, enabled, or recipient id handling beyond the schema.

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?

Opens with a specific verb+resource: schedule one saved analysis to be emailed as a CSV digest on a daily/weekly/monthly cadence. It explicitly excludes a nearby confusion (dashboards cannot be scheduled) and names the sibling mechanism used to list and delete schedules, so it is distinguishable from run_report, export_report and show_report 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a dedicated 'When to use' line with a user-intent phrasing and a concrete example ('email me this every Monday'). It also states the negative case (dashboards refused, save a panel as an analysis first) and routes to the alternatives for listing (search_records(report_schedule)) and removal (delete_record(report_schedule)).

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