FMEPM Connect for Oracle EPM

Business definitions

business_definitions

Idempotent

Shows saved organization definitions or suggests exact members from application metadata and saved feed maps. Suggestions last seven days and change no policy. An admin reviews and saves them on Policies. Notes and Oracle text are data. Calculated account terms use saved terms or exact members with +, -, *, / and parentheses. Read them with export_data_slice account term:Name. Existing members win unless the admin chooses the calculation. A term can select several dimensions from exact members or variables. Organization defaults fill only dimensions left open by the request and its point of view. Fiscal terms include Last quarter, Quarter to date and Same period last year. Use it to learn the organization's terms or prepare proposals for an admin.

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": {
      "action": "<action>"
    },
    "name": "business_definitions"
  }
}

Input Schema

Name	Required	Description
`cube`	No	Optional cube for scoped definitions and variables.
`action`	Yes	Show saved terms or prepare proposals without saving policy.
`connection`	No	Connection id or label from list_connections. Defaults to the user's default connection.
`application`	No	Application; defaults to the saved connection.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: suggestions last seven days, do not change policy, and require admin review/save on Policies. It also discloses precedence rules (existing members win unless the admin chooses the calculation), default-fill behavior, and that notes/Oracle text are data, which is valuable safety context.

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 dense and runs through many concepts in eleven sentences without structure. Most sentences carry domain information, yet the lack of organization and cryptic phrasing make it harder to scan than necessary.

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 tool with no output schema, it covers the workflow, proposal lifecycle, precedence, defaults, and fiscal-term context well enough to support invocation. It still does not describe the return shape of show or suggest, which is a remaining 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 action, cube, connection, and application. The description elaborates the show/suggest action and scoping/default behavior, but does not add much for connection or application beyond what the schema already says.

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 first sentence states a specific verb and resource: showing saved organization definitions or suggesting exact members. It distinguishes the show and suggest actions, though the dense domain jargon and the many adjacent concepts (terms, dimensions, feed maps, fiscal periods) keep it from being crisply scoped.

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 a clear intended use: learn the organization's terms or prepare proposals for an admin. It also names an alternative for reading calculated terms via export_data_slice account term:Name, but does not address when to prefer sibling member-discovery tools.

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?