Skip to main content
Glama
Sign In

FMEPM Connect for Oracle EPM

by com.fmepm.mcp
OverviewDiscussionsAdmin

Run a mapped EPM Automate command

epm_automate_command
Destructive

Resolves an EPM Automate command name to my REST catalog. Use it when a user names an EPM Automate command. No CLI process runs. arguments is the matching tool's JSON arguments, not shell text or CLI flags. Reads, writes, jobs, policy, previews and Activity use the same path as the matching tool. list_rest_operations shows parameters, applicability and verified status. Confirmation may be supplied inside arguments or at the top level; the top level takes precedence. Unsupported commands return a reason and nearest route. encrypt, help, login, logout and upgrade run on your computer. 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": {
      "command": "<command>"
    },
    "name": "epm_automate_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesOne of the 207 reviewed command names, with its exact case.
confirmNoSet true after the user has approved the previewed change
argumentsNoJSON arguments for the mapped catalog tool: application, params, query, body, or fileName and content for file tools. No command line is executed.
connectionNoSaved connection id or label.
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.2/5.0
Behavior5/5

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

Annotations already declare destructive/openWorld/non-idempotent, and the description adds substantial context on top: no CLI process executes, arguments are the mapped tool's JSON rather than shell text, and every write requires a preview followed by confirm:true plus a single-use confirmationToken valid for ten minutes. It also discloses failure behavior (unsupported commands return a reason and nearest route).

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?

Sentences are short and dense with information, with the core purpose front-loaded. The middle section jumps between arguments semantics, list_rest_operations, confirmation precedence, local commands and the token flow, so it reads as a list of facts rather than a structured narrative, but nothing is padding.

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 destructive, open-world dispatcher over 207 commands, the description covers the critical dimensions: semantics of arguments, the preview/confirm token protocol, local-only commands, and unsupported-command behavior. It does not describe the success response shape (no output schema exists) or the role of the connection parameter.

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 baseline is 3; the description goes beyond it by clarifying that 'arguments' is the mapped catalog tool's JSON arguments, not shell text or CLI flags, and that confirmation may appear inside arguments or at top level with top-level precedence. The 'connection' parameter is never addressed.

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?

States a specific, unusual operation: resolving an EPM Automate command name to the REST catalog, and explicitly negates the obvious misreading with 'No CLI process runs.' An agent can distinguish it from epm_rest_read/epm_rest_write/run_business_rule, though the description never names those siblings for contrast.

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?

'Use it when a user names an EPM Automate command' gives a clear trigger, and the exclusions for encrypt, help, login, logout and upgrade tell the agent when not to use it. It also routes discovery to list_rest_operations and states that unsupported commands return a reason and nearest route. Lacks an explicit statement of when to prefer a direct sibling tool over this dispatcher.

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 toolsInspect
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