FMEPM Connect for Oracle EPM

Read Oracle users and groups

read_oracle_directory

Read-onlyIdempotent

Lists Oracle users, groups or user-group memberships. Optional details include group membership and assigned roles. Oracle documents the users and groups list as read-only POST endpoints; they create no report file and change no account or assignment. Identity URLs, credentials and arbitrary fields are omitted. This pod-wide read refuses application-restricted policies. Oracle's Access Control permissions still apply. Use it to find users and groups before an access review. https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/lcm_list_users.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": {
      "action": "<action>"
    },
    "name": "read_oracle_directory"
  }
}

Input Schema

Name	Required	Description
`name`	No	Optional user login for users or memberships, or group name for groups.
`limit`	No	Maximum metadata records, counting memberships and roles too.
`action`	Yes	Directory list to read.
`details`	No	Include memberships and roles in user or group lists as separate metadata records.
`indirect`	No	Include indirect user group and role assignments when details is true.
`groupName`	No	Optional group filter for the memberships report.
`connection`	No	Connection id or label from list_connections. Defaults to the user's default connection.
`groupTypes`	No	Optional group types for the groups list.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses that these are read-only POST endpoints, that no report file is created and no assignment changed, that identity URLs/credentials are omitted, that pod-wide reads refuse application-restricted policies, and that Access Control permissions still apply. This is rich, non-redundant behavioral context.

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?

Purpose is front-loaded and most sentences earn their place with permission and safety detail. The Oracle-documentation sentence and trailing URL are somewhat heavier than needed but not wasteful.

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 an 8-parameter read tool with no output schema, the description covers purpose, permissions, data omission, and usage context well. It doesn't hint at return shape or pagination/limit behavior, which is a minor 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 all 8 parameters including enums and defaults. The description only loosely echoes the details/membership semantics and adds no syntax or interaction guidance beyond the schema, so baseline 3 is appropriate.

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 (lists) and precise resources (Oracle users, groups, memberships), and the enum-backed action makes the three modes explicit. It is clearly distinguishable from siblings like change_oracle_security and read_access_reports.

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?

"Use it to find users and groups before an access review" gives a concrete usage context. It stops short of naming the alternatives (read_access_reports, export_access_report) or stating when not to use it, so it's clear but not fully routing.

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?