FMEPM Connect for Oracle EPM

Upload a file

upload_file

Destructive

Uploads UTF-8 text or base64 bytes, at most 10 MiB, to the Oracle inbox or outbox. I show the filename, destination and byte count first. Confirm the exact preview before I send it. An existing file is not overwritten. Use it to send an input file before a data or metadata job. ZIP snapshot extraction is a separate migration workflow in list_rest_operations. For a write, I require a preview first, then confirm: true and its confirmationToken. The token lasts ten minutes and works once.

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": {
      "fileName": "<fileName>"
    },
    "name": "upload_file"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Set true after the user has approved the previewed change
`content`	No	File content as UTF-8 text or canonical base64. At most 10 MiB after decoding.
`encoding`	No	How content is encoded.	text
`fileName`	Yes	File name only, without folders.
`connection`	No	Connection id or label from list_connections. Defaults to the user's default connection.
`destination`	No	Oracle file destination.	inbox
`confirmationToken`	No	Single-use token from this exact preview. Send it with confirm: true after the user approves. It expires after ten minutes.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds real context beyond them: a mandatory preview step, a single-use confirmationToken that expires in ten minutes, and the no-overwrite guarantee. The one gap is that it never says what happens if the token is expired or reused, or what the preview actually returns beyond filename/destination/byte count.

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 capability and limits, then the confirmation protocol, then the alternative. Slightly padded by the first-person phrasing ('I show', 'before I send it') and by restating the token's ten-minute lifetime twice, but no sentence is wasted.

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?

For a mutating upload with seven parameters and no output schema, the description covers the payload constraints, destination choice, collision behavior, and the full two-call confirmation handshake. An agent can execute the flow correctly without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns the extra point by explaining the sequencing that the schema cannot — preview first, then 'confirm: true' together with the matching confirmationToken, and that the token is bound to 'this exact preview'. Encoding and connection parameters are left to the schema, which already covers them.

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 plus the accepted payload forms and size ceiling ('Uploads UTF-8 text or base64 bytes, at most 10 MiB, to the Oracle inbox or outbox'), which separates it from download_file and the REST/migration siblings. The destination enum is named inline, so scope is unambiguous.

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?

Explicitly says when to use it ('send an input file before a data or metadata job') and rules out a nearby confusion ('ZIP snapshot extraction is a separate migration workflow in list_rest_operations'). It also states the negative behavior an agent needs before calling: an existing file is not overwritten.

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?