Skip to main content
Glama

FMEPM Connect for Oracle EPM

Export data

export_data

Runs an Export Data job definition of the connected application (name from list_job_definitions) and returns the exported rows in one step: submit the job, wait for it, download the zip from the outbox, extract it and parse the csv. rowMembers, columnMembers and povMembers narrow the export the way the job definition allows; where keeps only the rows whose columns contain given text (for example a year in the Point-of-View column) and columns picks the columns to return. Large results are paged with offset and maxRows under the policy's cell limit, and nextOffset says where the next page starts. If the job is still running when waitSeconds is over, the result says so with the job id and file name to follow up with check_job_status and download_file. Use it to pull actuals, plan or forecast data for a whole cube region without building a grid.

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": {
      "jobName": "<jobName>"
    },
    "name": "export_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryNoName of the file inside the zip to read, from the entry list. Defaults to the only entry, or the largest csv/txt.
whereNoKeep only rows whose column contains the text, case-insensitive, e.g. { "Point-of-View": "FY24", "Account": "4310" }. Paging, totalRows and nextOffset then count the matching rows.
offsetNoData rows to skip before the first returned row (default 0). Use nextOffset from the previous result to page.
columnsNoColumns to return, in this order, e.g. ["Account", "TP1", "Point-of-View"]. Defaults to every column.
jobNameYesExport Data job definition name, exactly as list_job_definitions shows it, e.g. NSP_NFS_All_Data_Export
maxRowsNoRows to return per call (default 200, at most 2000). The policy cell limit can lower it.
connectionNoConnection id or label from list_connections. Defaults to the user's default connection.
povMembersNoPoint of view override as Oracle's povMembers parameter, e.g. NSP_Actual,FY24,Subsidiary
rowMembersNoRow members override as Oracle's rowMembers parameter, e.g. ILvl0Descendants(Account)
applicationNoApplication name. Defaults to the connection's application.
waitSecondsNoSeconds to wait for the job before handing back the job id (default 120, at most 300)
columnMembersNoColumn members override as Oracle's columnMembers parameter, e.g. TP1,TP2,TP3
exportFileNameNoOutbox file name for the export. Defaults to <jobName>_claude.zip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses the full workflow beyond the annotations: it submits a job, waits, downloads from the outbox, extracts the zip, parses CSV rows, applies paging under a policy cell limit, and returns nextOffset. It also explains the timeout behavior and the job id/file name needed for follow-up, which is substantial context not captured by the annotations.

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?

It is long but appropriately dense for a 13-parameter workflow tool, and the core action is front-loaded. Each sentence carries operational value about filtering, paging, timeout handling, or follow-up.

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?

Given the complex 13-parameter schema and absence of an output schema, the description compensates by explaining the returned rows, paging via nextOffset, and what is returned when the job is still running. An agent has enough information to invoke it and interpret the main result paths.

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 schema already documents most parameters well. The description adds useful integrated semantics for rowMembers, columnMembers, povMembers, where, columns, offset/maxRows paging, and waitSeconds, though it does not add much for entry, connection, application, or exportFileName beyond what the schema says.

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?

The description states a specific action chain: run an Export Data job definition, wait for it, download the zip, extract it, and parse the CSV. It distinguishes this from alternatives by saying it pulls data for a whole cube region without building a grid and by referencing list_job_definitions for the job name.

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?

It explicitly says to use the tool for actuals, plan, or forecast data across a whole cube region without building a grid. It also names the follow-up tools check_job_status and download_file when waitSeconds expires before the export finishes, and tells the agent where jobName comes from.

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