Skip to main content
Glama
test-task-server

test-task-server

by shazamlll

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
submit_test_taskA

Queue a test task for execution. Returns a task id; poll get_task_result for the outcome. Optional params.expectedOutcome ('passed' | 'failed') forces a deterministic outcome, useful for demos.

get_task_resultB

Return the status and result summary of a test task by id.

list_test_tasksA

List all submitted test tasks with their current statuses.

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

Disambiguation5/5

Each tool has a clearly distinct role: submit queues a task, get_task_result retrieves one task's outcome by id, and list_test_tasks enumerates all tasks. There is no meaningful overlap between submission, single-result polling, and listing.

Naming Consistency5/5

All three tools follow a consistent verb_noun pattern (submit_test_task, get_task_result, list_test_tasks) with snake_case throughout. The naming is predictable and readable.

Tool Count4/5

Three tools is on the thin side but matches the minimal async-task lifecycle the server advertises. Each tool earns its place with no filler.

Completeness4/5

The core submit/poll/list workflow is covered, which is sufficient for demo-grade test task tracking. However, there is no cancel or delete operation, leaving tasks with no lifecycle termination beyond completion.