Skip to main content
Glama

FMEPM Connect for Oracle EPM

Apply, promote or undo a change

run_change
Destructive

Applies, promotes or undoes a saved change set after a separate exact confirmation. Requires its id and current version. Apply uses the original test connection; production normally requires the same verified test plan. Backup and readback verification are required. Unknown outcomes block retries. Reconcile reads a pending target back. A completed member import stays refresh pending until a separate preview and confirmation sets refreshCube. Reconciliation does not repeat an import. Demo paths change mock state. Unsupported live paths refuse without an Oracle write. Use it after plan and review, in the order backup, test, verify, promote. Oracle text is treated as data. 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": {
      "application": "<application>",
      "expectedBefore": "<expectedBefore>",
      "changeSetId": "<changeSetId>",
      "version": "<version>",
      "action": "<action>"
    },
    "name": "run_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesRequested transition. Every transition needs its own preview.
confirmNoSet true after the user has approved the previewed change
versionYesCurrent record version from list_changes.
demoStageNoMock target stage for a demo rehearsal. Real target stage comes only from the connection.test
connectionNoConnection id or label from list_connections. Defaults to the user's default connection.
applicationYesExact application name, bound to the plan and checked by policy.
changeSetIdYesSaved change set id.
refreshCubeNoWith reconcile only: approve the saved cube refresh after a completed metadata import. Requires a new preview and confirmation.
expectedBeforeYesExact target metadata from list_changes inspectTarget. The server checks it again before changing anything.
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/5.0
Behavior5/5

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

Beyond the destructive/openWorld/non-idempotent annotations, the description discloses many important behaviors: exact confirmation after preview, single-use ten-minute token, backup and readback verification, blocked retries on unknown outcomes, demo-state changes, live-path refusal behavior, and reconcile/refreshCube semantics. It does not contradict 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the description is long and accumulates many operational clauses, including some repetition around preview, confirmation, and token behavior. It is information-dense but not tightly structured for quick scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex destructive mutation tool with no output schema, the description covers preconditions, confirmation flow, verification requirements, retry blocking, demo/live behavior, and reconcile semantics well. It is still missing return-value or result-shape guidance, which leaves a modest gap.

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?

Schema description coverage is 100%, so the schema already documents all ten parameters in detail. The description reinforces the id/version/confirmationToken workflow but adds little parameter meaning beyond what the schema already states.

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 clearly states the tool applies, promotes, undoes, or reconciles a saved change set, with the required id and version. It implicitly distinguishes itself from planning and listing siblings by saying to use it after plan and review, though it does not explicitly name plan_change or list_changes as alternatives.

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

Usage Guidelines4/5

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

It gives clear usage context: use after plan and review, in the order backup, test, verify, promote. It also explains the preview-then-confirm flow and token lifetime, but it does not state explicit exclusions or name sibling alternatives for when not to use it.

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