TNL
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_impacted_tnlsA | Return TNL units whose declared paths overlap with any of the given code paths. Repo-wide units are always included. |
| retrieve_tnlA | Return the verbatim content of TNL units identified by id. Ids with no matching file are listed in notFound. |
| traceA | Record or read session events documenting how TNL was used. Pass |
| propose_tnl_diffA | Stage a proposed TNL change (batch of creates and updates) for human review. Returns a diff_id for later approve_tnl_diff. |
| approve_tnl_diffA | Apply a staged proposal: write each tnl/.tnl, regenerate its sidecar, and remove the staging record. |
| verifyA | Verify the TNLs impacted by a set of code paths. Returns a structured report; verify failures are data, not isError. |
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 6 tools
Each tool has a distinct purpose: proposal staging, approval, impact analysis, retrieval, tracing, and verification. No overlap.
All tools follow a consistent verb_noun pattern using snake_case, making them predictable and easy to understand.
With six tools, the server covers the core workflow for TNL management without being too sparse or overburdened.
The set covers proposing, approving, retrieving, verifying, and tracing. Missing a list or delete operation, but the core lifecycle is well-represented.