FMEPM Connect for Oracle EPM

Build a Smart View workbook

build_smart_view_report

Read-onlyIdempotent

mode is required: functions for shared-connection HsGetValue report sheets that refresh, or members for plain member grids with no formulas. A call without mode fails with a message naming both choices. Functions mode includes cached numbers, two-column variances and companion Grid sheets. Shared POV arguments apply to up to ten tabs, each with a title, row and column dimensions and local member overrides. Two or more function tabs share a Control sheet whose members apply to every Report tab on Refresh All. All tabs together must fit the policy's cell limit. Notes explains the selected connection. Functions mode can use a named private connection. Demo data stays plain numbers. Returns a download link for one hour. Use it to take numbers into Excel.

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": {
      "mode": "<mode>"
    },
    "name": "build_smart_view_report"
  }
}

Input Schema

Name	Required	Description
`pov`	No	Members for any other dimension, for example { Version: "NSP_Base", Currency: "USD" }; dimensions you leave out use their top member
`mode`	Yes	Required user choice: functions for Refresh All, or members for ad hoc analysis. Required.
`rows`	No	Dimension names to put on rows, e.g. ["Account", "Department"]. Defaults to the account dimension.
`tabs`	No	Up to ten report tabs. Shared POV is given at the top level. A tab may override members with pov or scenario/year/entity/period/account. Rows and columns name axis dimensions.
`year`	No	Year member, e.g. FY26 or FY24
`fresh`	No	Set true to ignore the scenario, year, entity, cube and pov remembered from the user's previous request, start from scratch and read Oracle again even inside the policy's cache window.
`title`	No	Workbook title and file name
`entity`	No	Entity member, e.g. North America. Goes to the cube's entity-like dimension (Entity, Subsidiary, Company).
`period`	No	Period 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.
`account`	No	Account member or comma-separated list, e.g. Revenue or Descendants(Net Income). Defaults to all level 0 accounts.
`appName`	No	Application name. Defaults to the connection's application.
`columns`	No	Dimension names to put on columns, e.g. ["Period"] or ["Period", "Scenario"]. Defaults to the period dimension.
`planType`	No	Cube (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.
`scenario`	No	Scenario member, e.g. Actual, Plan, NSP_Actual
`connection`	No	Connection id or label from list_connections. Defaults to the user's default connection.
`includeData`	No	false omits cached numbers and leaves member grids empty; default true
`planningData`	No	Set 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.
`privateConnection`	No	Exact Smart View private connection name for functions mode. Keep its spaces and case; no # or \|. Members mode ignores it.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well past the readOnly/idempotent annotations: it discloses that a call without mode fails with a message naming both choices, that all tabs must fit the policy's cell limit, that two or more function tabs share a Control sheet affecting Refresh All, that demo data stays plain numbers, and that the return is a download link valid for one hour. The one-hour TTL and the error behavior are exactly the kind of operational detail annotations cannot carry.

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?

Nearly every sentence carries real information, but the ordering is poor: it opens on a parameter constraint rather than purpose, and the facts arrive as a dense run-on sequence with no grouping into purpose / modes / tabs / constraints / output. It reads as a brain dump rather than a structured brief.

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 18-parameter tool with nested tab objects and no output schema, the description covers the essentials an agent needs: mode selection, tab and POV composition, the cell-limit constraint, the Control sheet interaction, the returned link and its expiry. Remaining parameter-level detail is fully carried by the schema.

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?

With 100% schema description coverage, the schema already documents all 18 parameters, so the baseline is 3. The description adds some meaning beyond it, characterizing what each mode actually produces (refreshable HsGetValue sheets vs formula-free member grids) and the shared-POV-across-ten-tabs model, but it largely restates the schema for tabs, privateConnection and demo data.

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 conveys that this builds a downloadable Smart View workbook made of report tabs, and the closing line 'Use it to take numbers into Excel' anchors the purpose. It never front-loads a clean verb+resource statement and does nothing to distinguish it from sibling export tools like export_data or export_data_slice.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Strong internal guidance on the mode choice — 'functions for shared-connection HsGetValue report sheets that refresh, or members for plain member grids with no formulas' — tells the agent exactly how to pick the required enum. But there is no guidance on when to reach for this tool instead of the many sibling export/report tools, and no stated prerequisites such as needing a connection first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FMEPM Connect for Oracle EPM tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?