Skip to main content
Glama

FMEPM Connect for Oracle EPM

Submit a job

epm_rest_run_job
Destructive

Submits one job to an application through POST /jobs by catalog id (see list_rest_operations), for example exportData, importData, cubeRefresh or clearCube, and returns the job id to follow with check_job_status. The job type comes from the operation (or from body.jobType for executeJob); body carries jobName and parameters as Oracle documents them. Use it for job types the dedicated tools lack. Change sets are the safer option for metadata imports, member sorting and valid-intersection imports. Oracle's reference: https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/ 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": {
      "operationId": "<operationId>"
    },
    "name": "epm_rest_run_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJob body: { jobName, parameters, ... } and jobType when the operation is executeJob
confirmNoSet true after the user has approved the previewed change
connectionNoConnection id or label from list_connections. Defaults to the user's default connection.
applicationNoApplication name. Defaults to the connection's application.
operationIdYesCatalog id of a job operation, e.g. exportData, cubeRefresh, runRule
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?

Annotations already declare destructive=true, non-idempotent, openWorld, but the description adds critical contract detail the annotations cannot: a preview is required first, then confirm: true with a single-use confirmationToken valid for ten minutes. It also states the tool returns a job id for polling, and points at Oracle's reference for body shapes.

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 action and endpoint, then routing, then the confirm mechanism. It is dense and every sentence carries information, though the bare Oracle URL and the repetitive explanation of the confirmation token (repeated again in the schema) cost a little.

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 destructive, open-world job submission with no output schema, the description covers invocation routing, the body contract, the two-step confirmation gate and the follow-up tool for tracking. Nothing material is missing for an agent to call it correctly.

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, but the description adds real semantics: the job type is derived from the operation except for executeJob where body.jobType applies, and body carries jobName/parameters as Oracle documents them. This clarifies the nested free-form body, which the schema only gestures at.

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 ("Submits one job to an application through POST /jobs by catalog id") and names the mechanism (operationId catalog id, see list_rest_operations). It also distinguishes itself from siblings by naming check_job_status for follow-up and the dedicated job-type tools it complements.

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?

Explicit routing guidance: use this for job types the dedicated tools lack, and prefer change sets for metadata imports, member sorting and valid-intersection imports. It also mandates the preview-then-confirm workflow, which tells the agent exactly when a second call is required.

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