Skip to main content
Glama

FMEPM Connect for Oracle EPM

Get job details

get_job_details
Read-onlyIdempotent

Returns job details and Oracle's counts by dimension or load type. For a job in Error, reads ERROR messages from up to 25 child jobs, or WARNING messages if those children have no errors, with up to five messages per child. Requires Oracle's Service Administrator role. Use it when check_job_status shows an error and the user wants to know why.

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": {
      "jobId": "<jobId>"
    },
    "name": "get_job_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesJob id
connectionNoConnection id or label from list_connections. Defaults to the user's default connection.
applicationNoApplication name. Defaults to the connection's application.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only, idempotent annotations, the description adds meaningful operational context: the required Service Administrator role, the 25-child-job limit, the ERROR-then-WARNING fallback logic, and the five-messages-per-child cap. These are material execution details an agent needs before invoking the tool.

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 three sentences, front-loaded with what is returned and then drilling into the error case, permissions, and usage trigger. Every sentence contributes distinct information without repetition.

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 still explains what the tool returns, how error and warning messages are selected from child jobs, and the authentication prerequisite. That is complete enough for an agent to call it correctly and interpret the result.

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 three parameters. The description does not add parameter-level syntax or format details, but it does contextualize the jobId by discussing error jobs and child jobs, which is enough for the baseline 3.

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: returns job details plus Oracle counts by dimension or load type. It also distinguishes this tool from check_job_status by explaining the error-investigation use case, so an agent can select it 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?

It explicitly names check_job_status as the triggering tool and the condition ('shows an error and the user wants to know why'), which is strong usage guidance. It does not cover when to use this instead of related tools like export_job_history or list_recent_jobs for general job inspection, so it falls just short of full alternatives coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources