Skip to main content
Glama

apex_add_lov

Create a List of Values (LOV) for Oracle APEX select items, using either static display/return pairs or a SQL query to supply dropdown options.

Instructions

Create a List of Values (LOV) — static or SQL-based — for select items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lov_nameYesUnique name for this LOV (e.g., "DEPARTMENTS", "STATUS_LIST"). Referenced by name in apex_add_item(lov_name=...).
lov_typeNoType of LOV: - "sql": Dynamic LOV from SQL query (default) - "static": Static list of display/return value pairssql
sql_queryNoSQL query for type="sql". Must return 2 columns: display value, return value. Example: "SELECT department_name d, department_id r FROM departments ORDER BY 1" The column aliases 'd' and 'r' are conventional but any names work.
return_columnNoExplicit return column name (auto-detected from SQL if omitted).
static_valuesNoList of dicts for type="static". Each dict: {"display": "...", "return": "..."} Example: [{"display": "Active", "return": "Y"}, {"display": "Inactive", "return": "N"}]
display_columnNoExplicit display column name (auto-detected from SQL if omitted).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

The description only states 'Create', which implies a write operation, but adds no additional behavioral disclosure beyond what the annotations already indicate. It does not mention side effects, permissions, idempotency, or reversibility. With all annotations false, the description carries the burden but fails to provide meaningful transparency beyond the action.

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 a single, front-loaded sentence that conveys the essential purpose without any fluff. It is appropriately sized for the tool's complexity and does not waste words.

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

Completeness3/5

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

The tool has an output schema and rich parameter descriptions (100% coverage), so the description does not need to explain return values or parameter syntax. However, the description is minimal and does not provide context about integration with pages/items or any prerequisites. It is adequate but leaves room for more contextual guidance, especially for a creation tool.

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 parameters are well-documented in the schema. The description adds a high-level hint that the LOV can be 'static or SQL-based', which corresponds to the lov_type parameter and gives context for parameter selection. However, it does not explain parameter semantics beyond what the schema already covers, so the baseline 3 is appropriate.

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?

Description clearly states the action 'Create' and the resource 'List of Values (LOV)', with 'static or SQL-based' and 'for select items' adding specificity. This distinguishes it from sibling tools like apex_list_lovs (listing) and apex_add_item (creating items).

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?

The description provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The phrase 'for select items' hints at context, but there is no mention of when to choose static vs SQL-based or how to reference the LOV in other tools. The schema note about referencing in apex_add_item is helpful but not part of the main description.

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