Schema | TNL

TNL

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`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 `event` to record; omit it to read.
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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/janaraj/tnl'

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