Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MIST_HOSTNoJuniper Mist host if your cloud is not api.mist.com.api.mist.com
MIST_API_TOKENNoJuniper Mist API token.
CENTRAL_BASE_URLNoHPE Aruba Networking Central base URL.
CENTRAL_CLIENT_IDNoHPE Aruba Networking Central client ID.
CLEARPASS_BASE_URLNoHPE Aruba Networking ClearPass base URL.
CLEARPASS_API_TOKENNoHPE Aruba Networking ClearPass API token.
CENTRAL_CLIENT_SECRETNoHPE Aruba Networking Central client secret.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Network tools for HPE Aruba Central, Juniper Mist, HPE Aruba ClearPass, HPE Aruba UXI and HPE OpsRamp. Call find_tool with what you want to do, then invoke_read_tool for reads and checks, or invoke_tool for changes. access_check says what each login can do, and lists any extra named Central logins; pass login= to invoke_read_tool or invoke_tool to use one.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

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

Tools

Functions exposed to the LLM to take actions

NameDescription
find_toolA

Find the tool for a task. Call this first.

    query: what you want to do, in plain words ("bounce port 7 on the
    closet switch") or an exact API call ("GET /api/v1/sites/{site_id}").
    product: central, mist, clearpass, uxi, opsramp or specs (the API document lookup).
    Each hit has name, product, summary, kind (read, troubleshoot, config,
    disruptive, firmware, delete or admin) and label (read, diagnostic, write
    or destructive; a show-only check is troubleshoot with label read). Pass include_schema
    to get the arguments a tool takes. Then call invoke_read_tool (kind
    read or troubleshoot) or invoke_tool.
    
invoke_read_toolA

Run a tool that only reads, or a non-disruptive troubleshooting check (ping, show). Names come from find_tool.

    Cable tests can interrupt a link and require invoke_tool.

    A tool that can change something is refused with "not_a_read_tool".
    cursor: the next_cursor from a reply that was cut short, to get the rest.
    login: a named Central login from access_check (default: the main one).
    all_pages: fetch every page of a list here (up to 50 pages / 10,000 items) instead of one.
    fields: keep only these keys of each item ("radio.channel" reaches inside); cuts big replies.
    group_by: return a count per value of this field instead of the items ("firmwareVersion").
    Together they answer site-wide questions in one call: all_pages + group_by="status".
    
invoke_toolB

Run any tool from find_tool, including ones that change the network.

    The tool's own kind (from find_tool) says what it changes.
    login: a named Central login from access_check (default: the main one).
    
access_checkB

What each product login can do, and whether this server is read-only.

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 4 tools

Disambiguation4/5

The workflow is clearly staged: find_tool discovers, access_check reports permissions, and the two invoke tools execute. The only fuzzy boundary is invoke_read_tool vs invoke_tool, since invoke_tool claims to run 'any tool from find_tool', including reads, but the read variant's extra pagination/field/group_by options make the intended split understandable.

Naming Consistency4/5

All names are snake_case and readable, with two clear verb_verb_noun pairs (invoke_read_tool, invoke_tool) and find_tool. access_check breaks the verb_noun pattern by being noun-first, a minor deviation rather than a real inconsistency.

Tool Count4/5

Four tools is a sensible fixed facade for a gateway that multiplexes six products via dynamic discovery. There is slight redundancy in having invoke_tool capable of doing everything invoke_read_tool does, but the extra read-only conveniences justify keeping both.

Completeness4/5

Discovery, permission inspection, schema retrieval (include_schema), pagination, and both safe and destructive execution are all covered, which is solid for a meta-server. Gaps are minor: there is no way to enumerate all available tools or list by product without a free-text query, and no login/credential management beyond naming a login.

Maintenance

ActivityActive
ResponsivenessNo recent community issues