Skip to main content
Glama

apex_add_combo_chart

Add a combo chart (bar + line) to an Oracle APEX page. Specify SQL for bar and line series to visualize both metrics on shared axes.

Instructions

Add a combo chart (bar + line on same axes). SQL: LABEL, BAR_VALUE, LINE_VALUE.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
heightNoChart height in pixels.
labelsNoOptional dict to override labels. Supported keys: ``"bar"`` (bar legend), ``"line"`` (line legend).
bar_sqlYesSQL for the bar series. Must return bar_label_col and bar_value_col. Example: "SELECT TO_CHAR(DT_AVALIACAO,'MM/YYYY') LABEL, COUNT(*) VALUE FROM TEA_AVALIACOES GROUP BY TO_CHAR(DT_AVALIACAO,'MM/YYYY') ORDER BY 1"
page_idYesTarget page ID.
bar_nameNoLegend name for bar series.Volume
line_sqlYesSQL for the line series. Must return line_label_col and line_value_col. Example: "SELECT TO_CHAR(DT_AVALIACAO,'MM/YYYY') LABEL, ROUND(AVG(NR_PCT_TOTAL),1) VALUE FROM TEA_AVALIACOES WHERE NR_PCT_TOTAL > 0 GROUP BY TO_CHAR(DT_AVALIACAO,'MM/YYYY') ORDER BY 1"
sequenceNoDisplay order on page.
animationNoAnimation style — "auto", "none", "fade", or "zoom".auto
line_nameNoLegend name for line series.Trend
region_nameYesRegion display name.
y_axis_titleNoLeft Y-axis (bar) label.
zoom_enabledNoEnable zoom on chart axes (default False).
bar_label_colNoX-axis column in bar_sql (default "LABEL").LABEL
bar_value_colNoY1-axis column in bar_sql (default "VALUE").VALUE
color_paletteNoList of hex colours, a named palette string, or None.
y2_axis_titleNoRight Y-axis (line) label.
line_label_colNoX-axis column in line_sql (default "LABEL").LABEL
line_value_colNoY2-axis column in line_sql (default "VALUE").VALUE
scroll_enabledNoEnable scroll on chart (default False).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations are all false (not read-only, not idempotent, not destructive), which alerts the agent that this is a mutating operation, but the description itself adds no behavioral context. It does not mention what side effects occur (e.g., region creation), permissions needed, or return behavior.

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 description is a single concise sentence that front-loads the primary purpose. It is efficient, but the brevity sacrifices critical detail needed for a 19-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (19 parameters, 4 required, output schema present), the description is severely under-specified. It does not explain the relationship between bar_sql and line_sql, how to map columns, or any configuration caveats beyond the schema defaults.

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

Parameters2/5

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

Although the schema covers 100% of parameters, the description's SQL hint 'LABEL, BAR_VALUE, LINE_VALUE' is ambiguous and potentially contradictory with the schema's separate bar_sql and line_sql parameters. This can mislead an agent about how to structure the SQL queries.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool adds a combo chart with bar and line on the same axes, which distinguishes it from other chart types among the many sibling chart tools. However, it does not explicitly call out alternatives or nuance beyond the basic definition.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not explain when to choose this over other chart tools (e.g., area chart, stacked chart) nor any prerequisites or context for use.

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

Install Server

Other Tools

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/TechFernandesLTDA/apex-mcp'

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