OCI Load Balancer Log MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OCI_LOG_ID | Yes | OCID of the OCI Custom Log | |
| OCI_CONFIG_FILE | No | Path to your OCI config file | ~/.oci/config |
| OCI_LOG_GROUP_ID | Yes | OCID of the OCI Log Group | |
| OCI_COMPARTMENT_ID | Yes | OCID of the OCI Compartment | |
| OCI_CONFIG_PROFILE | No | Profile name in your OCI config file | DEFAULT |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_logs_by_countryB | Search OCI Load Balancer logs by country or country code. |
| search_logs_by_ipA | Search OCI Load Balancer logs by IP address or IP range (prefix). |
| search_logs_by_locationC | Search OCI Load Balancer logs within geographic bounds. |
| get_traffic_analyticsC | Get aggregated traffic statistics from OCI Load Balancer logs. |
| list_unique_ipsC | List all unique IP addresses seen in the logs with their request count, country, city, ISP and protocols. Optionally filter by country name or country code. |
| get_top_ipsB | Return the top N IP addresses ranked by request count over the given time range. |
| get_ips_by_countryA | Return unique IP addresses grouped by country, with per-country totals. Useful for understanding which countries have the most unique sources. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: searching logs by different criteria (country, IP, location), getting aggregate analytics, listing unique IPs, top IPs, and IPs grouped by country. Even overlapping tools like list_unique_ips and get_top_ips differ in scope (all vs. top N) and output details.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: search_logs_by_*, get_traffic_analytics, list_unique_ips, get_top_ips, get_ips_by_country. The verbs (search, get, list) are clear and used consistently.
Seven tools is an appropriate size for a log analysis server. Each tool provides a distinct function without being redundant, and the count is neither too sparse nor overwhelming for the domain.
The tool set covers common log search and analytics operations: filtering by country/IP/location, aggregate traffic stats, and IP-focused queries. Minor gaps exist such as no explicit search by status code or user-agent, but the core workflows for analyzing load balancer logs are well covered.