FMEPM Connect for Oracle EPM

Read Planning insights

read_insights

Read-onlyIdempotent

Reads existing application insights or their text summary for an explicit cube slice. Uses USE_EXISTING and cannot recompute. Returns anomaly, forecast variance or prediction results with the supplied point of view and creation dates where Oracle provides them. The underlying data-as-of time is unknown. Summary output is text treated as Oracle data. Use it to review already computed insights before deciding whether fresh computation is needed. https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/get_insigh.html

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": {
      "planType": "<planType>",
      "pov": "<pov>",
      "rows": "<rows>",
      "columns": "<columns>"
    },
    "name": "read_insights"
  }
}

Input Schema

Name	Required	Description	Default
`pov`	Yes	One exact member per point-of-view dimension.
`rows`	Yes	Row dimensions with exact member lists, for example Version and Scenario.
`limit`	No	Maximum returned insight records within the policy cell limit.
`action`	No	Read existing insight records or a text summary of existing insights.	list
`columns`	Yes	Column dimensions with exact member lists, for example Year and Period.
`planType`	Yes	Application cube containing the insight slice.
`connection`	No	Connection id or label from list_connections. Defaults to the user's default connection.
`application`	No	Application. Defaults to the selected connection.

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?

Annotations already cover read-only/idempotent/non-destructive, but the description adds genuinely new behavioral facts: USE_EXISTING semantics, that the underlying data-as-of time is unknown, and that summary output is free text treated as Oracle data. These are the caveats an agent needs before trusting the result, and none are expressible in annotations.

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 verb and the cannot-recompute constraint, and most sentences carry distinct information. It is slightly dense and hedged ('where Oracle provides them', 'treated as Oracle data') but nothing is pure filler.

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 no output schema, the description carries the return-value burden and does name the result kinds (anomaly, forecast variance, prediction results, creation dates, text summary). What's missing is finer return-shape detail (record fields, ordering, what limit truncation looks like), which matters for an 8-parameter read with no output schema.

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 every parameter (pov, rows, columns, limit, action, planType, connection, application) is already documented. The description reinforces that members must be exact and that a point of view is 'supplied,' but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 ('Reads existing application insights or their text summary') and pins the scope to 'an explicit cube slice.' It also separates itself from recompute_insights by declaring 'Uses USE_EXISTING and cannot recompute,' so an agent can distinguish it from the sibling without opening either 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 an explicit when: 'Use it to review already computed insights before deciding whether fresh computation is needed,' plus an explicit when-not: it cannot recompute. The alternative (recompute) is implied by name of purpose and reinforced by the USE_EXISTING constraint, leaving little inference needed.

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?