Skip to main content
Glama

apex_add_master_detail

Create master-detail Interactive Reports on the same APEX page. Clicking a master row refreshes the detail region using a linked column.

Instructions

Create master IR + detail IR on same page. Row click in master refreshes detail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesPage ID where both regions will live.
sequenceNoDisplay sequence for the master region (detail gets +10).
detail_sqlYesSQL query for the detail IR. Must reference the hidden item as a bind variable. Example: ``"SELECT * FROM TEA_BENEFICIARIOS WHERE ID_CLINICA = :P10_SELECTED_ID"``
master_sqlYesSQL query for the master IR. Example: ``"SELECT ID, DS_NOME FROM TEA_CLINICAS ORDER BY DS_NOME"``
link_columnYesColumn in the master IR whose value is passed to the hidden item when a row is clicked (e.g., ``"ID"``).
page_item_nameYesSuffix for the hidden item name — auto-prefixed with ``P{page_id}_``. The bind variable in ``detail_sql`` must match.
detail_region_nameYesDisplay name of the detail IR region.
master_region_nameYesDisplay name of the master IR region.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description discloses a key behavior—row click in master refreshes detail—which is valuable. However, it does not mention other side effects such as the creation of a hidden item or dynamic actions, and the annotations are all false, providing no safety context. The description carries the burden but only partially covers the behavioral impact.

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 two short, front-loaded sentences with no filler. Every word contributes to understanding the tool's purpose and key behavior, making it an excellent example of concise communication.

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

Completeness4/5

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

Given the rich schema descriptions and availability of an output schema, the description does not need to explain return values or parameter details. It provides the essential behavior (master-detail interaction) and is complete enough for an agent to understand the tool's role, though it could mention prerequisites like existing page.

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?

With 100% schema description coverage, the schema already thoroughly documents all parameters, including the hidden item binding and SQL examples. The description adds no additional parameter-level meaning, so the baseline score of 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?

The description clearly states the verb 'Create' and the resource 'master IR + detail IR on same page', which precisely defines the tool's function. It also distinguishes from sibling tools like apex_add_region or apex_generate_crud by specifically targeting an interactive report master-detail pairing.

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?

The context of creating master-detail IRs on the same page is clearly conveyed, and the row-click refresh behavior implies the intended use case. However, the description doesn't explicitly mention alternatives or when not to use this tool, so it falls short of a full 5.

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