Skip to main content
Glama
jasperan

OraViz MCP

by jasperan

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOG_LEVELNostructlog level number20
LOG_FORMATNojson (default) or consolejson
ORACLE_DSNNoFull EZConnect descriptor; overrides host/port/service
ORACLE_HOSTNoDatabase hostnamelocalhost
ORACLE_PORTNoListener port1521
ORACLE_USERYesDatabase user (required)
ORACLE_SERVICENoService nameFREEPDB1
ORACLE_PASSWORDYesPassword for the user (required)
ORACLE_CONFIG_DIRNoWallet config directory (Autonomous Database / mTLS)
ORACLE_CALL_TIMEOUTNoPer-statement timeout, seconds (0 disables)60
ORACLE_MCP_MAX_ROWSNoHard row cap per query500
ORACLE_MCP_BIND_HOSTNoBind host for network transports127.0.0.1
ORACLE_MCP_BIND_PORTNoBind port for network transports8080
ORACLE_CONNECT_TIMEOUTNoTCP connect timeout, seconds10
ORACLE_WALLET_LOCATIONNoWallet location
ORACLE_WALLET_PASSWORDNoWallet password
ORACLE_MCP_PREVIEW_ROWSNoDefault preview size for execute_query25
ORACLE_MCP_MAX_CELL_CHARSNoPer-cell truncation limit500
ORACLE_MCP_SERVER_TRANSPORTNostdio (default), http, sse, streamable-httpstdio

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
execute_queryA

Executes a read-only SELECT/WITH query and returns a compact markdown table plus a metadata line (row count, and whether more rows exist). Results are preview-capped by default to protect the caller's context: aggregate in SQL and only pass max_rows when the raw rows are really needed. Large cell values are summarised.

list_tablesA

Retrieves a list of all tables and views available in the configured Oracle schema as a compact markdown table. Optionally takes a schema name.

get_table_schemaA

Retrieves the schema of a table or view as a compact markdown table: column name, data type, length, nullability, and whether the column is part of the primary key.

sample_table_dataA

Retrieves a small sample of rows from the specified table as a compact markdown table. sample_size controls how many rows to return (default: 10, capped by the server).

get_table_detailsA

Retrieves table details: owner, tablespace, optimizer statistics (NUM_ROWS, BLOCKS, AVG_ROW_LEN, LAST_ANALYZED) and, optionally, an exact row count.

profile_tableB

Profiles a table for visualization: row count plus per-column statistics (non-null count, distinct count, min, max, average) to decide which chart fits the data.

create_chartA

Runs a read-only SQL query and renders the result as a chart image (PNG). chart_type is one of: bar, line, area, scatter, pie, histogram. The first column is the x-axis or labels; numeric columns after it become series. Returns the image plus a data preview.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation4/5

Most tools target clearly distinct operations, but a few boundaries require careful reading: create_chart and execute_query both run SQL, and get_table_details and get_table_schema both describe table metadata. The descriptions clarify the outputs enough that an agent should usually pick correctly.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: execute_query, list_tables, get_table_schema, sample_table_data, get_table_details, profile_table, create_chart. The naming is predictable and uniform across the set.

Tool Count5/5

Seven tools is well-scoped for an Oracle exploration and visualization server. Each tool serves a distinct discovery or charting purpose without unnecessary bloat or missing core functionality.

Completeness4/5

The server covers the full exploration-to-visualization workflow: listing objects, inspecting schema, sampling data, profiling columns, running queries, and creating charts. Minor gaps exist, such as no table DDL viewer or chart configuration options, but an agent can accomplish the intended tasks without dead ends.