Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HAC_URLNoHAC base URL. Default `https://localhost:9002/hac`.https://localhost:9002/hac
HAC_PASSYesHAC password.
HAC_USERYesHAC user.
HAC_LOG_PATHNoPath to the local console log file. Required for `logs_tail`.
HAC_TIMEOUT_MSNoRequest timeout in ms. Default 30000.30000
HAC_ALLOW_REMOTENoSet to `true` to allow a `HAC_URL` that is not a private host.false
HAC_INSECURE_TLSNoSet to `true` to accept self-signed certificates (typical for local HAC). Off by default.false

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
flexible_searchB

Read-only. Run HAC FlexibleSearch against the configured local HAC. Optional translate=true returns generated SQL only.

logs_tailB

Read-only. Tail the local SAP Commerce/HAC console log. Optional grep filters the tailed source lines.

type_infoB

Read-only. Return SAP Commerce type attributes, deployment data, and subtypes via a tenant-safe Groovy template.

config_getA

Read-only. Return a configuration property by key, or all visible keys when key is omitted. Values of keys matching pass/secret/token/key/credential are masked.

beans_infoB

Read-only. Return Spring bean implementation and aliases using the HAC application context.

monitoring_infoA

Read-only. Return cluster, memory, threads, cache, or thread-dump diagnostics via tenant-safe Groovy.

cronjobB

Read-only. List cronjobs (action=list) or return the status of one by code (action=status).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a clearly distinct diagnostic resource: FlexibleSearch queries, console logs, type metadata, configuration properties, Spring beans, monitoring diagnostics, and cronjobs. There is no meaningful overlap in purpose, so an agent can reliably select the right tool.

Naming Consistency4/5

Most tools follow a consistent snake_case resource-oriented pattern (flexible_search, logs_tail, type_info, config_get, beans_info, monitoring_info). The only notable deviation is the bare noun 'cronjob', which is still readable but breaks the pattern slightly.

Tool Count5/5

Seven tools is well-scoped for a lightweight read-only SAP Commerce/HAC diagnostic server. Each tool covers a distinct operational area and earns its place without redundancy.

Completeness4/5

The tool set covers the core read-only diagnostic surface: querying, logs, type metadata, config, beans, monitoring, and cronjobs. Minor gaps exist around broader extension/package inspection or more granular cronjob operations, but these are reasonable omissions for a 'lite' read-only server.

Maintenance

ActivityMaintained
ResponsivenessSyncing