Skip to main content
Glama
ruya-grp

fusion-query-mcp

by ruya-grp

fusion_run_query

Read-onlyIdempotent

Run read-only SQL SELECT queries on Oracle Fusion Cloud data. Substitutes lexical parameters and enforces a row cap for safe result exploration.

Instructions

Run a read-only SQL SELECT -- ONLY on a pod that substitutes lexical parameters.

Check whether this tool can work here before you use it. It ships the statement as a lexical BI Publisher parameter, and a Fusion pod that has lexical substitution disabled (the common SaaS hardening, and the case this server was built for) silently drops it: the data model then executes SELECT * FROM () and Oracle answers ORA-00903. No rewrite of your SQL fixes that, so do not enter a repair loop -- the failure hint says so explicitly when it sees that signature.

The working path on such a pod is the report registry: call fusion_list_reports to see what an administrator has already built, then fusion_run_report to run one with bind values and fusion_validate_report to check it. Schema exploration works either way.

If your pod does honour lexicals, this is the full free-SQL surface. The statement must be a single SELECT or WITH; anything else is rejected before it leaves this machine, and a row cap is appended automatically unless the SQL already limits rows. Give every selected expression a simple alias (SUM(x) AS TOTAL_AMOUNT) -- result columns become XML element names, and unaliased expressions can produce an unparsable document.

Args: sql: The SELECT/WITH statement to execute. datasource: Configured datasource key (default: the server's default). max_rows: Row cap for this call, clamped to the server's hard maximum. timeout_s: Per-call timeout in seconds. select_list: engine_mode: clauses only -- the projection without SELECT. from_clause: engine_mode: clauses only -- the FROM body without FROM. where_clause: engine_mode: clauses only -- including the WHERE keyword. group_clause: engine_mode: clauses only -- including GROUP BY/HAVING. order_clause: engine_mode: clauses only -- including ORDER BY/FETCH.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sqlNo
max_rowsNo
timeout_sNo
datasourceNo
from_clauseNo
select_listNo
group_clauseNo
order_clauseNo
where_clauseNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses critical failure behavior: lexical substitution may be silently disabled, the statement could become `SELECT * FROM ()`, and no SQL rewrite fixes it. It also reveals that the tool appends a row cap, rejects anything not a single SELECT/WITH, and can produce unparsable XML output if expressions lack aliases.

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 long but every section earns its place: a front-loaded warning, a clear alternative path, a precise scope statement, and a compact parameter list. It is structured with bolded warnings and separators that make the critical information easy to scan.

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?

Given the tool's complexity, zero schema coverage, and a non-obvious failure mode, the description covers everything needed to invoke it correctly: prerequisites, failure signature, workaround path, SQL constraints, row-cap behavior, alias rules, and per-parameter semantics. An output schema exists, so not detailing return values is acceptable.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries full responsibility, and it delivers. It explains all 9 parameters in the Args list, including the engine_mode clause-building parameters, the meaning of max_rows clamping, timeout_s, and datasource defaulting, plus the alias requirement for selected expressions.

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 clearly states a specific verb and resource: 'Run a read-only SQL SELECT -- ONLY on a pod that substitutes lexical parameters.' It distinguishes this tool from the report-registry path and explicitly frames it as the 'full free-SQL surface,' making its identity 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?

The description gives explicit when-to-use and when-not-to-use guidance: check whether the pod honors lexical parameters, avoid a repair loop if the ORA-00903 signature appears, and instead use fusion_list_reports followed by fusion_run_report and fusion_validate_report. This directly names alternatives and the condition that selects them.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ruya-grp/Fusion-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server