FMEPM Connect for Oracle EPM

Get dimension metadata

get_dimension_metadata

Without a dimension, lists the dimensions of an application with their types. With a dimension, returns its members with parent, alias, generation and level. Generation starts at 1 for a top member and increases by 1 for each child. Level is 0 for a member with no children; a parent is one more than the highest level among its children. On a live pod this may run the Export Metadata job, which can take a few minutes. Use it to learn member names before exporting data, or to explain an outline.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_dimension_metadata"
  }
}

Input Schema

Name	Required	Description
`dimension`	No	Dimension name, e.g. Account. Omit to list the dimensions.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4/5.0

Behavior4/5

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

The description explains a non-obvious side effect that justifies the non-readOnly annotation: on a live pod it may trigger the Export Metadata job and take minutes. That is genuinely useful context the agent would otherwise miss. It does not cover auth requirements, error modes, or whether the job blocks subsequent calls.

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 mode split, then the latency warning, then the use cases. The generation/level explanation is the densest part but is justified since there is no output schema and these semantics are otherwise unknowable. Slightly more output-shape detail than strictly needed for the call decision.

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?

With no output schema, the description carries the return-value burden and does so: it names the member fields returned (parent, alias, generation, level) and defines generation and level precisely. Combined with the latency warning and mode split, an agent has enough to call this correctly.

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 coverage is 100%, so all three parameters are already documented with examples and defaults. The description reinforces the important omit-to-switch-modes semantics of 'dimension' 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a precise verb+resource and cleanly splits the two modes: listing dimensions of an application vs returning members of one dimension. It is clear on its own, but it never distinguishes itself from near-neighbours such as list_dimension_members, find_members, or export_metadata, so an agent must infer the boundary.

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 supplies concrete usage contexts ('learn member names before exporting data', 'explain an outline'), which is more than most definitions offer. It stops short of explicit exclusions or naming an alternative tool for overlapping cases.

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?