iz-tolk-mcp
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_compiler_versionA | Returns the version of the Tolk compiler (from @ton/tolk-js WASM). Use this to check which compiler version is available. |
| compile_tolkA | Compiles Tolk smart contract source code using @ton/tolk-js. Provide source files as a map of filename->content. The entrypoint file must be included. Standard library imports (@stdlib/, @fiftlib/) are resolved automatically. Supports pathMappings for custom @alias import resolution. Returns compiled Fift code, BoC (Bag of Cells) in base64, code hash, and compiler version. |
| check_tolk_syntaxA | Checks Tolk source code for syntax and type errors without returning full compilation output. Faster feedback loop for iterative development. Supports pathMappings for custom @alias import resolution. Returns OK + code hash on success, or error details on failure. |
| generate_deploy_linkA | Generates a TON deployment deeplink for a compiled Tolk contract. Accepts the compiled code BoC (base64) and optionally initial data BoC. Computes the contract address and returns ton:// deeplinks for wallet deployment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| write_smart_contract | Guided workflow for writing a new Tolk smart contract on TON |
| review_smart_contract | Security-focused review of a Tolk smart contract |
| debug_compilation_error | Help diagnose and fix a Tolk compilation error |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| language-guide | Complete Tolk language syntax reference |
| stdlib-reference | Standard library modules and functions reference |
| changelog | Tolk compiler version history from v0.6 to latest |
| tolk-vs-func | FunC to Tolk migration guide — key differences and comparison |
| example-counter | Simple counter smart contract example in Tolk |
| example-jetton | Jetton (fungible token) minter contract example in Tolk |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: syntax checking, compilation, deploy link generation, and version retrieval. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_tolk_syntax, get_compiler_version), making them predictable and easy to understand.
With 4 tools, the server is well-scoped for Tolk smart contract development, covering essential operations without unnecessary bloat.
The tool set covers the main workflow: syntax check, compilation, and deploy link generation. However, it lacks tools for tasks like directly fetching contract addresses or deploying contracts, which are minor gaps.