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
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_instanceA

Create a new sandbox instance with a persistent workspace directory.

list_instancesA

List all active (non-archived) sandbox instances.

list_archived_instancesA

List all archived sandbox instances.

archive_instanceA

Archive a sandbox instance, disabling new job submissions.

update_instanceC

Update or get an instance's metadata (currently only description).

submit_jobA

Submit a command as an async (non-blocking) job.

poll_jobC

Poll a running job. Optionally wait for completion.

list_jobsA

List tracked jobs for an instance, newest first, with pagination.

cancel_jobA

Cancel a running job and return its final status and output tail.

host_execA

Run a pre-configured host command or list available commands.

With no argument, returns the list of configured host commands and their descriptions. With a command key, runs the matching host command outside any sandbox (directly on the host).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct resource and action: instance lifecycle, job lifecycle, and host commands are clearly separated. The only potential pairing, list_instances vs list_archived_instances, is explicitly disambiguated by 'archived' in both name and description.

Naming Consistency4/5

Most tools follow a snake_case verb_noun pattern (create_instance, list_jobs, cancel_job). host_exec deviates slightly by placing the noun before the verb, though it remains readable and consistent in style.

Tool Count5/5

Ten tools is well-scoped for an HPC sandbox service with instance management, asynchronous job execution, and host command access. Each tool covers a meaningful operation without unnecessary duplication.

Completeness4/5

The tool set covers the essential instance lifecycle (create, list, archive, update) and job lifecycle (submit, poll, list, cancel). Minor gaps exist, such as no direct single-instance getter, no unarchive/destroy operation, and limited job output retrieval outside poll/cancel.

Maintenance

ActivityStale
ResponsivenessNo issues