FMEPM Connect for Oracle EPM

Read snapshots and backups

read_snapshots

Read-onlyIdempotent

Lists snapshot metadata and retained backups, shows one snapshot's capabilities, or reads its artifact tree, modification history and migration status. The artifact and history reads use Oracle's documented read-only POST endpoints and create no export. Contents, logs and links are omitted. Backup names and Oracle time text are preserved without guessing a time zone. API availability and Oracle roles vary by pod. This pod-wide read is blocked by application-restricted policies. Use it to check available snapshots and backup dates before planning work. https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/migration_get_snapshot_list.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_snapshots"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum metadata records, up to 500. Large results are marked incomplete.
`action`	Yes	The metadata to read. No action downloads, restores, imports or deletes a snapshot.
`connection`	No	Connection id or label from list_connections. Defaults to the user's default connection.
`categoryName`	No	Exact migration category name for artifacts, such as HP-Vision.
`snapshotName`	No	Existing snapshot name for details, artifacts or history.

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?

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the artifact and history reads use documented read-only POST endpoints and create no export, contents/logs/links are omitted, backup names and time text are preserved without time-zone guessing, and access is pod- and role-dependent. These are exactly the behavioral traits an agent needs.

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?

The multi-mode purpose is front-loaded in the first sentence, followed by behavioral caveats. It is dense but nearly every clause carries information; the doc URL at the end is useful but slightly beyond the core need.

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 multi-action read tool with no output schema, the description covers safety, omissions, time-zone handling, and access variability. It could go further in clarifying what each action returns, but the explicit 'contents, logs and links are omitted' and the docs link largely compensate.

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 the schema documents all five parameters including the action enum and the limit cap. The description reinforces that no action downloads/restores/imports/deletes, but it does not add syntax or format meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource and enumerates the six action modes ('Lists snapshot metadata and retained backups, shows one snapshot's capabilities, or reads its artifact tree, modification history and migration status'). An agent can distinguish this read-only snapshot inspector from adjacent siblings like export_metadata or read_data_integration without opening the schema.

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 check available snapshots and backup dates before planning work' gives a concrete when-to-use context, and 'This pod-wide read is blocked by application-restricted policies' plus 'API availability and Oracle roles vary by pod' set preconditions. No sibling alternative is named, so it falls short of a 5.

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?