FMEPM Connect for Oracle EPM

Explain a variance

explain_variance

Read-onlyIdempotent

Reads Oracle totals and walks the account hierarchy to find the largest contributors to a change. Use it before explaining why a number changed. Compare two scenarios, versions or periods. Optionally break down one other business dimension. The difference is to minus from. Child sums are checked against Oracle totals with the reconciliation rules; every remainder is shown as other. Separate dimension breakdowns must not be added together. Account types set favorable or unfavorable; unknown types stay unclassified. Service Administrator access is needed for member properties. Read only.

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": {
      "cube": "<cube>",
      "member": "<member>",
      "comparison": "<comparison>",
      "pov": "<pov>"
    },
    "name": "explain_variance"
  }
}

Input Schema

Name	Required	Description
`pov`	Yes	One exact member for every other cube dimension. No assumed or remembered choices.
`top`	No	Largest contributors to show in each breakdown. Smaller ones go in other.
`cube`	Yes	Cube to read.
`depth`	No	Levels of children to inspect, at most eight. The cell limit applies across levels.
`member`	Yes	One exact account total, or term:Name for a saved account term.
`tolerance`	No	Absolute tolerance for each roll-up check, in the same units as the values.
`comparison`	Yes	Scenario, Version or Period dimension and two exact members. Change means to minus from.
`connection`	No	Connection id or label from list_connections. Defaults to the user's default connection.
`application`	No	Application; defaults to the connection.
`breakdownDimension`	No	One other business dimension, such as Entity. Its POV member is the branch root.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

It discloses important behavior beyond the annotations: child sums are reconciled against Oracle totals, remainders are grouped as other, separate dimension breakdowns must not be added together, and account types determine favorable/unfavorable classification. It also notes the Service Administrator access requirement for member properties and confirms read-only behavior, consistent with readOnlyHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is dense but front-loaded, opening with the core operation and immediately following with when to use it. Every sentence adds useful semantic or behavioral information, with no filler.

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 complex ten-parameter tool with no output schema, the description provides enough context to invoke it correctly: comparison semantics, breakdown behavior, reconciliation handling, remainder treatment, and access requirements are all covered. The annotations already carry the safety profile, and the schema carries detailed parameter definitions.

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 a few semantics, such as the comparison direction and one optional breakdown dimension, but those points largely repeat schema text rather than adding substantial new parameter-level meaning.

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?

The description states a specific verb and resource: it reads Oracle totals, walks the account hierarchy, and finds the largest contributors to a variance. It clearly explains what the tool computes, including the comparison direction and optional dimension breakdown, so an agent can distinguish it from generic read or reconciliation tools.

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?

The description gives clear usage context: use it before explaining why a number changed, and compare two scenarios, versions, or periods. It does not explicitly name alternative sibling tools such as reconcile_total or explain_answer, so the routing guidance is strong but not fully exclusive.

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?