Skip to main content
Glama
Anguraj-zoho

Elegant MCP Server

by Anguraj-zoho
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

get_page_blueprint

Obtain exact layout, component hierarchy, column names, data patterns, chart config, and sidemenu structure of a Log360 Cloud page. Call before building to ensure accuracy.

Instructions

Returns a detailed visual blueprint of a real Log360 Cloud page — exact layout, component hierarchy, column names, data patterns, chart config, and sidemenu structure. ALWAYS call this before building any page to understand the correct structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesPage name to get the blueprint for.

Implementation Reference

  • api/mcp.ts:667-671 (handler)
    The handler for the 'get_page_blueprint' tool. It looks up the requested page in the PAGE_BLUEPRINTS record and returns the layout specification. If the page is not found, it returns an error with the list of available pages.
    server.tool("get_page_blueprint", "Returns the exact layout specification for a real Log360 Cloud page — component hierarchy, column names, data patterns, chart config, sidemenu items. This is your ONLY reference for what the page looks like. Do NOT look for screenshots or HTML files locally.", { page: z.enum(Object.keys(PAGE_BLUEPRINTS) as [string, ...string[]]) }, async ({ page }) => {
  const bp = PAGE_BLUEPRINTS[page];
  if (!bp) return { content: [{ type: "text" as const, text: `Unknown page: ${page}.\n\nAvailable pages:\n${Object.keys(PAGE_BLUEPRINTS).join("\n")}` }] };
  return { content: [{ type: "text" as const, text: bp + `\n\n---\nCDN: ${CDN_BASE}\nAfter reading this blueprint, call get_shell() for the HTML skeleton, then get_component() for each component listed above.` }] };
});
  • api/mcp.ts:667-667 (schema)
    The input schema for get_page_blueprint: accepts a 'page' parameter which is a zod enum constrained to the keys of PAGE_BLUEPRINTS.
    server.tool("get_page_blueprint", "Returns the exact layout specification for a real Log360 Cloud page — component hierarchy, column names, data patterns, chart config, sidemenu items. This is your ONLY reference for what the page looks like. Do NOT look for screenshots or HTML files locally.", { page: z.enum(Object.keys(PAGE_BLUEPRINTS) as [string, ...string[]]) }, async ({ page }) => {
  • api/mcp.ts:277-557 (helper)
    The PAGE_BLUEPRINTS data record containing all page layout specifications. This is the static data that get_page_blueprint queries.
    const PAGE_BLUEPRINTS: Record<string, string> = {
"reports-windows-all-events": `# Blueprint: Reports > Servers & Workstation > Windows > All Events

## Layout (Shell C)
TopNavBar → data-active-tab="Reports"
QuickLink bar (line-tab): Servers & Workstation (selected) | Network Devices | Cloud Sources | ...
Sidemenu Type 2 (left): OS dropdown "Windows" + search + flat accordion sections
Main content: Header + input-row + classic-tab (chart) + table-scroll-area

## TopNavBar Row 2
Tab items: Servers & Workstation | Network Devices | Cloud Protection | Applications | Active Directory | Microsoft 365 | Cloud Sources | File Integrity Monitoring | Threats | VM Management | Custom Reports

## Sidemenu (flat accordion with chevron-right icons)
Sections (each has > chevron that rotates on expand):
- Windows Events (expanded by default, shows sub-items)
  - All Events (highlighted when active)
  - Important Events
  - User Based Activity
- Logon Reports >
- Device Severity Reports >
- Windows Startup Events > (expand to show: Windows Startup, Windows ShutDown, Windows Restarts, Unexpected Shutdown, System Uptime, Windows Startup and Windows ShutDown)
- USB Storage Auditing >
- System Events >
- Windows Firewall Auditing >
- Registry Changes >
- Service Audit >
- Eventlog Reports >
- Network Share Auditing >
- Local Account Management >
- Process Tracking >
- DNS Server >
- Policy Changes >
- Group Management >
- Logoff Reports >
- Failed Logon Reports >
- Windows Backup and Restore >
- Program Inventory >
- Application Whitelisting >
- Windows Important Events >
- Threat Detection from Antivirus >
- Threat Detection >
- Application Crashes >
- Network Policy Server >
- Wireless Network Reports >
- Powershell Auditing >

Bottom links: Scheduled Reports | Manage Reports | Need New Reports?

## Page Header (header-v3)
Title: "All Events" + help icon
Right buttons: Edit Report | Export As ▾ | Schedule Reports | More ▾

## Input Row (reports-input-row--type1)
Fields: Select Log Source [dropdown with IP tags] | Period [date range picker] | [Generate button blue]

## Classic Tab (chart toggle — ONE chart area, NOT two separate charts)
Tab headers: All Events (selected) | Top Source | Top Devices | Time Based View | TEST
Below tabs: ONE chart container with rpt-chart-floater toolbar (customize + chart/table toggle)
Chart: Line chart showing event count over time (x-axis: dates, y-axis: count)
Legend below chart: ● Error ● Warning ● Information ● Success ● Failure (color-coded)

⚠️ CRITICAL: This is ONE classic-tab with ONE chart area. The tab buttons switch between All Events / Top Source / Top Devices views. Do NOT create separate charts for each tab. Use classic-tab JS to toggle content panels.

## Table
ActionBar: [list/table view toggle] [Incident button] | pagination "1-10 of 3302351" [< >] [10 ▾] [columns icon]
Columns: [checkbox] | Source | Log Source | Severity | Event ID | Display Name | Source (rightmost) | Timestamp
Row data pattern: "2020-04-18 01:30:48 | server | success | 4689 | Server | microsoft-windows-security-auditing"
Rows show realistic Windows event log data with Event IDs like 4689, 4658, 4656, 7036.`,

"reports-windows-startup": `# Blueprint: Reports > Servers & Workstation > Windows > Windows Startup

## Layout (Shell C)
Same as "reports-windows-all-events" but sidemenu has "Windows Startup Events > Windows Startup" highlighted.

## Sidemenu
"Windows Startup Events" section is EXPANDED showing sub-items:
- Windows Startup (highlighted/active)
- Windows ShutDown
- Windows Restarts
- Unexpected Shutdown
- System Uptime
- Windows Startup and Windows ShutDown

## Page Header
Title: "Startup Events" (NOT "Windows Startup" — use the actual report title)

## Input Row
Fields: Select Log Source [dropdown "All Devices"] | Time Period [dropdown "Last 24 Hours"] | [Generate button blue]

## Classic Tab (Bar / Line toggle — ONE chart, toggle between views)
Tab headers: Bar (selected by default) | Line
ONE chart area with rpt-chart-floater.
Default view: Bar chart showing startup events count by device (x-axis: device hostnames, y-axis: event count)
Line tab: Line chart showing startup events over time (x-axis: dates, y-axis: count)

⚠️ CRITICAL: This is a classic-tab with Bar/Line toggle. There is ONE chart area. The classic-tab JS handles switching between bar and line views. Do NOT render two charts. Render ONE and use:
\`\`\`js
// In Bar tab content:
ElegantEChart.bar('mainChart', { labels:[...], datasets:[...] });
// In Line tab content (hidden by default):
// Chart renders on tab switch via classic-tab.js
\`\`\`

## Table
ActionBar: same as all-events (search + Incident + pagination + columns)
Columns: [checkbox] | Source | Event ID | Event Description | Source (IP) | Log Source Type | Event Generated | Timestamp
Row data pattern: Windows startup log entries with:
- Source: "EventLog" or "Service Control"
- Event ID: 6005, 6009, 7036, 10, etc.
- Event Description: "The Event log service was started", "Microsoft Windows...", "The following boot-start or system-start..."
- Log Source Type: "@Author"
- Realistic timestamps
Total rows: ~260 (show "1-50 of 260" in pagination)`,

"reports-unix-all-events": `# Blueprint: Reports > Servers & Workstation > Unix > All Events

## Layout (Shell C)
Same shell as Windows reports but OS dropdown in sidemenu set to "Unix/Linux".

## Sidemenu
OS dropdown: Unix/Linux (selected)
Sections: All Events (highlighted), Important Events, SU Logons, Logon Reports >, Failed Logon Reports >, System Events >, Terminal Service Session >, FTP Server Reports >
Bottom links: Scheduled Reports | Manage Reports | Need New Reports?

## Page Header (header-v3)
Title: "All Events" + help icon
Right buttons: Edit Report | Export As ▾ | Schedule Reports | More ▾

## Input Row
Fields: Select Log Source [dropdown] | Period [date range picker] | [Generate button blue]

## Classic Tab (chart toggle)
Tab headers: All Events (selected) | Top Source | Top Devices | Time Based View
ONE chart area with rpt-chart-floater. Line chart with severity breakdown.
Legend: ● Error ● Warning ● Information ● Success ● Failure

## Table
ActionBar: list/table view toggle | Incident | pagination | columns
Columns: [checkbox] | Source | Log Source | Severity | Event ID | Display Name | Source | Timestamp`,

"dashboard": `# Blueprint: Dashboard — Events Overview (Shell A)

## Layout (Shell A)
TopNavBar → data-active-tab="Home"
QuickLink bar (line-tab): Events Overview (selected) | Network Overview | AD Overview | AWS Overview | Microsoft 365 | File Monitoring | Incident Overview | PgSQL Overview | SQL Server Overview | AD Summary | Threat Analytics | Cloud Protection | Custom Tab 1
No sidemenu. Full-width scrollable main content. Date range picker in top-right.

## Stat Cards Row (4 cards, horizontal)
1. All Events: "4489K" with delta "▲ 4441,946 (3406.52%)" — blue icon
2. Windows Events: "3302K" with sub-stats
3. Syslog Events: "11444" with delta "▲ 9942 (471.63%)"
4. All Log Sources: "18" with link "View All Log Sources"

## Widget Grid (2 columns, 3 rows)
Row 1: "Log Trend" area chart | "Recent Alerts" scrollable list
Row 2: "Security Events" table | "Top 5 Log Sources" donut chart
Row 3: "Windows Severity Events" bar chart | "Syslog Severity Events" bar chart

## Key Rules
- Each widget uses the widget component
- Charts use ElegantEChart.* calls
- Incident Workbench floating button at bottom-right`,

"dashboard-network": `# Blueprint: Dashboard — Network Overview (Shell A)
Same as Events Overview but "Network Overview" tab selected in quicklink bar.
Stat cards + widget grid for network-specific data.`,

"alerts": `# Blueprint: Alerts (Shell D — no sidemenu)

## Layout
TopNavBar → data-active-tab="Alerts"
Line-tab: Alerts (selected) | Incident
No sidemenu — full-width content. Date range picker in top-right.
Right actions: Export As ▾ | Add Alert Profile | Manage Profiles

## Stat Cards Row (4 horizontal)
1. Critical Alerts: "184185" — red
2. Trouble Alerts: "6942" — orange
3. Attention Alerts: "222" — yellow
4. All Alerts: "191349" — blue

## Table (NO chart — directly below stat cards)
ActionBar: pagination "1-10 of 191349" [< >] [10 ▾] | Add/Remove Columns
Columns: [checkbox] | Severity | Profile Name | Time ▾ | Alert Message Format | Log Source

## Key Rules
- NO chart on this page — stat cards go directly to table
- Severity column shows colored labels
- Incident Workbench floating button at bottom-right`,

"alerts-manage-profiles": `# Blueprint: Alerts > Manage Profiles
Same TopNavBar + line-tab. Table: checkbox | Alert Type | Severity | Message | Log Source | Action`,

"compliance": `# Blueprint: Compliance — Landing Page (no sidemenu)

## Layout
TopNavBar → data-active-tab="Compliance"
Search bar at top-left | "Manage Compliance" link top-right
Grid (3 columns): each card has icon + title + description + "View Reports" button

### Row 1: PCI-DSS | HIPAA | FISMA
### Row 2: GDPR | SOX | ISO 27001:2013
### Row 3+: more compliance standards`,

"compliance-report": `# Blueprint: Compliance > PCI-DSS > Report Page (Shell C)

## Layout (Shell C)
Line-tab top: PCI-DSS (selected) | HIPAA | FISMA | GDPR | SOX | ...
Sidemenu Type 2: ← PCI-DSS back + accordion sections (Windows Logon Reports expanded)

## Page Header
"← PCI-DSS" back link + Title: "User Logons"
Right: Export As ▾ | date range

## Chart Area (single horizontal bar chart — NO classic-tab toggle)

## Table
ActionBar: list/table view toggle | pagination "1-10 of 299" [< >] [10 ▾] | columns
Columns: [checkbox] | Time | Log Source | User Name | Remote Device | Remote Domain | Domain | Logon Type | Process Id`,

"search": `# Blueprint: Search (custom layout)

TopNavBar → data-active-tab="Search" | No sidemenu
Search box: query input + Basic/Advanced tabs + Search button
Results: bar chart + list view (NOT table) with dense key-value fields per row
ActionBar: Incident button | pagination | Add/Remove Fields`,

"security": `# Blueprint: Security — Analytics Dashboard (Shell A variant)

TopNavBar → data-active-tab="Security" | No sidemenu

## Stat Cards (4): All Rules 81952 | Critical 48968 | Trouble 16247 | Attention 16737

## Widget Grid (3 columns)
Row 1: Detection Pipeline (stacked bar) | Detection by Tactics (radar/MITRE) | Recent Detections (list)
Row 2: Top 5 Users (bar) | Top 5 Log Sources (hbar)
Row 3: Top 10 Detections by Rules (bar) | Detection Trends (line, 3 series)

## Key Rules
- MITRE ATT&CK radar chart
- Color coding: Critical=#E24C4C, Trouble=#F5A623, Attention=#F8D648`,

"cloud-protection": `# Blueprint: Cloud Protection (Shell A variant)

Line-tab: Application Insight (selected) | User Insight | Date picker

## Stat Cards (4): Total Traffic 298.69GB | Total Request 50416 | Discovered Apps 28 | Shadow Apps 10

## Widget Grid (3 columns)
Row 1: Total Traffic Trend (area) | Top Cloud Apps (donut) | Top Banned Apps (table)
Row 2: Shadow Apps (bar) | Download Size (donut) | Upload Size (hbar)
Row 3: Top Categories (hbar) | Low Reputed Apps (bar)`,

"settings": `# Blueprint: Settings — Device Management (Shell B)

## Layout (Shell B)
TopNavBar → data-active-tab="Settings"
Sidemenu Type 1 (settings variant — icons, NOT flat accordion):
- 2 icon tabs: Configuration | Admin
- Sections with icons: Log Source Configuration (expanded: Devices, Applications, Import Logs, Manage Cloud Sources, File Integrity Monitoring), Cloud Protection Settings

## Page Header: "Device Management"

## Line Tab (below header)
Tabs: Windows Devices (7) (selected) | Syslog Devices (1) | Other Devices (7)

## Input Row
Select Category: [All Devices ▾] | "Configure domain/workgroups" link | [+ Add Device(s)] button

## Table
ActionBar: search | filter | action icons | pagination "1-10 of 64" [< >] [10 ▾] | view toggle
Columns: [checkbox] | Actions | Device ▾ | Show IP | Agent | Last Message Time ▾ | Next Scan On | Monitoring Interval | Log Source Group | Status
- Actions: 3 small icon buttons per row
- Status: "Listening for logs" (green), "Disabled" (red)`,

"settings-license": `# Blueprint: Settings — License Page (Shell B)
Same settings shell. Storage stats, feature table with usage bars, plan details.`,

"incident-workbench": `# Blueprint: Incident Workbench (floating panel)
Bottom-right panel on every page. Shows investigation tools (IP Threat Intel, Process Hunting, User Activity Overview).`,
};

Tool Definition Quality

A3.7/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only describes return contents but fails to disclose that the tool is read-only, non-destructive, or any side effects. Safety profile is missing.

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?

Two sentences, front-loaded with the primary purpose. The imperative usage note is valuable and concise. No wasted 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?

Given no output schema, the description lists many return details (layout, hierarchy, column names, etc.) but omits the output format (presumably JSON). It adequately covers the tool's purpose for a simple one-param tool, but could be more specific.

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 coverage is 100% with a well-described 'page' parameter (enum). The description adds broader context about real Log360 Cloud pages but does not elaborate on the parameter beyond what the schema provides. 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?

The description clearly specifies the tool returns a 'detailed visual blueprint of a real Log360 Cloud page' with exact layout, component hierarchy, etc. It distinguishes from siblings like get_component which returns individual components.

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?

Explicitly states 'ALWAYS call this before building any page to understand the correct structure.' Provides clear when-to-use context but lacks mention of when not to use or alternatives.

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/Anguraj-zoho/elegant-mcp'

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