FMEPM Connect for Oracle EPM

Call a read REST operation

epm_rest_read

Read-onlyIdempotent

Calls one read operation of the Oracle EPM REST API (GET or a documented read-only POST) by catalog id (see list_rest_operations) with path parameters, query string and a JSON body when required, and returns Oracle's JSON response. Only read operations are reachable here. Use it for reads the dedicated tools lack, such as one member, user variables, planning units or named connections. Oracle's reference: https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/

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_read"
  }
}

Input Schema

Name	Required	Description
`body`	No	JSON body for a documented read-only POST. listTheArtifactsInACategoryV2 accepts only { "categoryName": "Core" }, with no path or other filters. Filter returned records locally or use list_forms for paged form names. params holds path placeholders only.
`query`	No	Query string parameters, e.g. { limit: 100 }. File-output parameters are refused on reads.
`params`	No	Path parameters by placeholder name, e.g. { cube: "Plan1", name: "CurrMonth" }. app is filled from the application argument and must not be passed here.
`connection`	No	Connection id or label from list_connections. Defaults to the user's default connection.
`application`	No	Application name. Defaults to the connection's application.
`operationId`	Yes	Catalog id of a read operation, e.g. getMember, getUserVariables, getPlanningUnits

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value beyond that by stating the response is Oracle's raw JSON and that only read operations are reachable — including a narrow carve-out for documented read-only POSTs. It stops short of describing unknown-operation-id failures or any response envelope, which keeps it from a 5.

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 core action and scope in the first sentence, then the usage rule and the doc link. It earns almost every clause, though the closing reference URL is nice-to-have rather than decision-relevant for the agent.

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?

With six parameters, all fully documented in the schema, and a broad 90+ value enum, the description supplies the missing orientation: where the catalog ids come from and which tool covers the common cases. No output schema exists, but saying it returns Oracle's JSON is adequate for an escape-hatch tool; only error/pagination behaviour is left implicit.

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 description coverage is 100%, so baseline is 3. The description still adds meaning by framing operationId as a catalog id sourced from list_rest_operations and by outlining that the call needs path parameters, query string and a body when required — clarifying the relationship among the three object parameters rather than just restating them.

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 — calls one read operation of the Oracle EPM REST API by catalog id — and explicitly bounds the scope ('Only read operations are reachable here'). It also distinguishes itself from the many dedicated siblings by naming the cases it exists for (single member, user variables, planning units, named connections), so an agent can tell it apart from get_dimension_metadata, get_substitution_variables or list_rest_operations without opening any schema.

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?

Gives both sides of the routing decision: use it only for reads the dedicated tools lack, and only for GET or documented read-only POST. It also points to list_rest_operations as the source of valid catalog ids, which is the prerequisite step an agent needs before it can call this tool at all.

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?