ctxtest
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CTXTEST_DB_PATH | No | test.db | |
| CTXTEST_DATA_DIR | Yes | test. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hello-worldC | A simple hello world tool |
| statB | Check the status of the server |
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 2 tools
The two tools, hello-world and stat, have completely distinct purposes with no overlap. An agent can easily distinguish between them without confusion.
The naming conventions are not consistent: hello-world uses a hyphen and two words, while stat is a single word. This inconsistency could confuse an agent expecting a uniform pattern.
With only 2 tools, the server feels very thin. For a server named ctxtest, more tools would be expected to provide meaningful functionality beyond a hello world and status check.
The tool surface is too sparse to infer a clear domain. There are obvious gaps: no tools for configuration, error handling, or any context-related operations that the server name might imply.