Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
await_commandA

Block agent execution until a shell command exits with code 0 (success). The command is polled at regular intervals. The agent is stuck on this call until done.

Exit code convention:

  • Exit 0: condition met → return success

  • Exit 2: condition failed → return failure

  • Any other code: still running → keep polling

Use this to wait for long-running operations: cloud builds, CI/CD, deployments, etc. Example: await_command(command="curl -sf https://ci.example.com/build/123/status | grep -q done", interval_seconds=30)

await_urlA

Block agent execution until a URL returns the expected HTTP status code. Optionally check that the response body contains a specific string. The agent is stuck on this call until the condition is met or timeout.

Example: await_url(url="http://localhost:3000/health", expected_status=200)

await_fileA

Block agent execution until a file exists and optionally contains a specific string. Useful for file-based signaling between processes (e.g., build status files).

Example: await_file(path="/tmp/build-status", contains="SUCCESS")

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adlternative/await-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server