Skip to main content
Glama

FMEPM Connect for Oracle EPM

Create a scheduled report

create_scheduled_report
Destructive

Saves a data slice as a scheduled report that runs daily, on weekdays, weekly or monthly at a time in the user's time zone and builds a Smart View workbook (kind smartview) or a CSV file (kind csv). The file waits on the Schedules page until it expires, behind a sign-in to the portal by the owner or an organization admin. I store the definition under this user's connection and policy and return the Schedules page link and the next run time; nothing reaches Oracle until the first run, and every run shows on the Activity page under the user's name. Use it when the user wants the numbers they are looking at as a file every morning, every Monday or on a day of the month. Pass the same slice arguments as export_data_slice. For a write, I require a preview first, then confirm: true and its confirmationToken. The token lasts ten minutes and works once.

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": {
      "name": "<name>",
      "every": "<every>",
      "at": "<at>"
    },
    "name": "create_scheduled_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesThe time of day in the schedule's time zone, as HH:MM on the 24 hour clock, for example 07:30
povNoMembers for any other dimension, for example { Version: "NSP_Base", Currency: "USD" }; dimensions you leave out use their top member
kindNosmartview (the default) builds an Excel workbook laid out as a Smart View grid; csv writes the rows as a CSV file
nameYesA short name for the report, unique per person, for example Revenue by month
rowsNoDimension names to put on rows, e.g. ["Account", "Department"]. Defaults to the account dimension.
yearNoYear member, e.g. FY26 or FY24
everyYesdaily, weekdays (Monday to Friday), weekly (on weekday) or monthly (on dayOfMonth)
entityNoEntity member, e.g. North America. Goes to the cube's entity-like dimension (Entity, Subsidiary, Company).
periodNoPeriod member or comma-separated list, e.g. Jan, Q1 or TP1,TP2,TP3. Member functions such as ILvl0Descendants(YearTotal) work. Defaults to level 0 members under YearTotal.
accountNoAccount member or comma-separated list, e.g. Revenue or Descendants(Net Income). Defaults to all level 0 accounts.
appNameNoApplication name. Defaults to the connection's application.
columnsNoDimension names to put on columns, e.g. ["Period"] or ["Period", "Scenario"]. Defaults to the period dimension.
confirmNoSet true after the user has approved the previewed change
weekdayNoFor weekly: 0 (Sunday) to 6 (Saturday)
planTypeNoCube (plan type) to export from, e.g. Plan1 or NSP_NFS. When the application has one cube it is used; with several, pass one. Otherwise Plan1.
scenarioNoScenario member, e.g. Actual, Plan, NSP_Actual
timezoneNoAn IANA time zone such as America/Toronto, Europe/London or UTC (default America/Toronto); ask the user when unsure
connectionNoConnection id or label from list_connections. Defaults to the user's default connection.
dayOfMonthNoFor monthly: 1 to 28, so every month has the day
planningDataNoSet true to read through the application's form engine (Smart List labels, form-level security) instead of the plain cube export. The cube export is the default because the form engine returns nothing when a parent member is in the point of view.
confirmationTokenNoSingle-use token from this exact preview. Send it with confirm: true after the user approves. It expires after ten minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: nothing is sent to Oracle until the first run, the artifact sits on the Schedules page until expiry behind an owner/admin sign-in, the definition is stored under the user's connection and policy, and every run is attributed on the Activity page. It also explains the two-step preview/confirm requirement and token lifetime, which an agent cannot infer from destructiveHint/openWorldHint alone.

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?

Purpose is front-loaded in the first clause, followed by lifecycle, then usage guidance and the confirm flow, so an agent can stop reading early. It is dense and somewhat long, with a few clauses (connection/policy storage, Activity page attribution) that are useful but could be trimmed.

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 21-parameter destructive, open-world write with no output schema, the description supplies the return values (Schedules page link and next run time), the safety gate, the timezone expectation, and the artifact lifecycle — enough for an agent to call it correctly without further inference.

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% and each of the 21 parameters is already documented, including enum values and day/month bounds, so the baseline is 3. The description adds genuine cross-tool semantics by saying to pass the same slice arguments as export_data_slice and by explaining the required preview/confirm pairing, but it does not restate per-parameter formats.

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 ("Saves a data slice as a scheduled report") plus the exact cadence options and output artifacts (Smart View workbook or CSV). It is clearly distinguishable from siblings like export_data_slice (one-off export) and list_scheduled_reports (read-only listing).

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?

Gives an explicit trigger phrase ("when the user wants the numbers they are looking at as a file every morning, every Monday or on a day of the month"), names the alternative for one-off needs by telling the agent to pass the same slice arguments as export_data_slice, and spells out the mandatory preview-then-confirm:true workflow with its single-use ten-minute token.

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