NexaLayer Agent
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| nexalayer_check_statusA | Check NexaLayer service status before retrying or filing a ticket. Returns each component (api, sessions, billing, catalog, upstream_network) as operational, degraded_performance, partial_outage, major_outage, or under_maintenance, plus active incidents and recent incident history. If the component your call depends on is not operational, wait and retry later instead of reporting an issue. No API key needed; no charge. |
| nexalayer_known_issuesA | List known issues with machine-runnable workaround steps. Call this with the error_code from a failed tool call (for example UPSTREAM_UNAVAILABLE or BACKEND_ERROR) before filing a ticket; if an issue matches, run its workaround.steps instead of reporting. No API key needed; no charge. |
| nexalayer_report_issueA | File a support ticket with NexaLayer. Use only after following the error's suggested_action and checking nexalayer_check_status and nexalayer_known_issues. Recent request_ids and error codes seen by this MCP server are attached automatically, so you do not need to copy them. The server assigns severity (S1 outage or wrong billing, S2 broken with no workaround, S3 bug with a workaround, S4 question or feature request). Returns ticket_id and next_check_after_seconds; poll with nexalayer_get_ticket. Never include API keys, proxy passwords, or full_url: they are redacted and the ticket is escalated as a security issue. No charge. |
| nexalayer_get_ticketA | Read a NexaLayer support ticket: status (received, triaged, needs_info, in_progress, awaiting_approval, workaround_available, resolved, closed), severity, events, matched known issue with workaround steps, and resolution. Poll no sooner than next_check_after_seconds. No charge. |
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 16 tools
Each tool targets a distinct resource-action pair across clearly separated domains: sessions (create/get/rotate/terminate/usage/health), budget (set/get/alerts), billing (balance/transactions), support (status/known_issues/report/get_ticket), and catalog (list_products). The closest pairs—session_health vs session_usage and get_budget vs usage_alerts—are differentiated by descriptions (health/rotation vs traffic, limits/spend vs threshold alerts). No two tools appear to do the same thing.
All tools share the nexalayer_ prefix and snake_case, and most follow a verb_noun pattern (get_balance, list_transactions, create_session, rotate_session, report_issue). A few are noun phrases rather than verb-first (session_health, usage_alerts, known_issues, session_usage), a minor deviation from the otherwise predictable pattern.
16 tools sit at the upper end of the comfortable range but each earns its place across five functional areas (sessions, budget, billing, support, catalog). The count is slightly heavy but reasonable for the breadth of the service being governed.
Core lifecycle coverage is strong: create/get/rotate/terminate plus usage and health for sessions, set/get budget with alerts, balance and transactions for billing, and a full support loop (status, known_issues, report, get_ticket). The notable gap is the absence of a list_sessions operation to enumerate existing sessions, a minor inconvenience rather than a dead end.