TurnSignal
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TURNSIGNAL_TOKEN | Yes | TurnSignal project token from https://app.turnsignal.ai (read-only use) | |
| TURNSIGNAL_API_URL | No | Only for a self-hosted TurnSignal server (default https://app.turnsignal.ai) |
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 |
|---|---|
| turnsignal_recent_runsA | Recent CI runs of this project, newest first: verdict, status, branch, commit, counts and run id. Use it to find a run to inspect. |
| turnsignal_runA | One run explained: the verdict, and every failed, flaky or missing test with its file:line, error message, code snippet, whether the failure is new or already on the default branch, and links to its trace/video/screenshot. Pass runId, or runKey (e.g. "github:1234567"), or neither for the latest run. |
| turnsignal_test_historyA | One test's recent results across runs (newest first): outcome, branch, run. Use it to tell a new breakage from a long-flaky test. testKey comes from turnsignal_run. |
| turnsignal_flaky_testsB | Tests that were flaky (failed, then passed on retry) in the last N days, most flaky first, with counts. |
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 4 tools
Each tool targets a clearly distinct scope: recent_runs lists runs, run details a single run, test_history tracks one test across runs, and flaky_tests aggregates flaky tests over a time window. The descriptions explicitly state the progression (find a run, inspect it, drill into a test) so an agent can pick the right tool without overlap confusion.
All names use a consistent turnsignal_ prefix with snake_case, giving a predictable pattern. The only minor wrinkle is the noun-phrase style (run vs recent_runs, test_history, flaky_tests) with a singular/plural pair that could momentarily blur, but it remains readable and coherent.
Four tools is a tight, well-scoped set for a read-only CI test inspection domain, with each tool covering a distinct layer (runs, run detail, test history, flaky aggregation). No tool feels redundant or missing at this scale.
The surface covers the core diagnostic lifecycle: find runs, explain a run, trace a single test over time, and surface flaky tests. Minor gaps exist (e.g. no way to list all tests in a run, compare runs, or fetch raw logs), but agents can work around these via the run detail tool.