Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
nexalayer_list_productsB

List a compact catalog of current products and prices before purchasing.

nexalayer_create_sessionA

Create a paid network session. This action incurs charges against the account balance. Configure a budget first and obtain owner approval for autonomous spend. The create API does not honor include_credentials and omits proxy credentials; read the session with include_credentials=true. Credentials are omitted unless include_credentials=true; never log them. PRICE_MISMATCH (409: re-read prices, retry once). BUDGET_EXCEEDED and INSUFFICIENT_BALANCE (402: ask the owner, don't retry).

nexalayer_get_sessionA

Read one session's status and proxy endpoint. Credentials are omitted unless include_credentials=true; never log them.

nexalayer_rotate_sessionA

Rotate a dynamic session after health or telemetry recommends rotation. Credentials are omitted unless include_credentials=true; never log them.

nexalayer_terminate_sessionA

Terminate a session and release its underlying network resource. Early termination does not imply a refund.

nexalayer_session_healthB

Read health score and rotation recommendation for a session.

nexalayer_session_usageC

Read traffic and request usage for a session.

nexalayer_get_budgetA

Read spend limits, current spend, pause state, and next daily reset.

nexalayer_set_budgetB

Set key and daily spend limits. This is a consequential write and should require owner approval.

nexalayer_usage_alertsB

Read actionable budget threshold alerts.

nexalayer_get_balanceA

Read the current account balance and trial-credit state.

nexalayer_list_transactionsC

List billing transactions for audit and reconciliation.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct resource or action: account balance, budget read/write, transactions, session usage, alerts, product catalog, and session lifecycle operations. Overlaps are minimal, and descriptions clarify financial reads (balance vs. budget) and session reads (usage vs. health vs. get_session).

Naming Consistency4/5

All tools share the nexalayer_ prefix and most follow a clear verb_noun pattern (get_balance, create_session, terminate_session). Three tools (session_usage, usage_alerts, session_health) are noun phrases without a verb, which is a minor deviation from the otherwise consistent convention.

Tool Count5/5

With 12 tools, the set covers account/billing and session management without obvious redundancy, and each operation has a clear purpose. This is well within the ideal range for the domain.

Completeness4/5

Core lifecycle is covered: read balance, budget, transactions, usage, alerts, and products; set budget; and create/get/rotate/terminate/health-check sessions. Missing list_sessions (and possibly explicit budget pause/resume or product detail) are minor gaps that agents can work around if session IDs are known.

Maintenance

ActivityMaintained
ResponsivenessNo issues