Loading ToolBench

Reading the current corpus…

izTolkMcp MCP server · F · ToolBench

izTolkMcp

MCP server for Tolk smart contract compiler — compile, analyze, and explore TON smart contracts from any MCP-compatible AI assistant

2026-07-28+STDIO4 tools

11/100

Definition Quality0

Protocol Readiness0

Supportability38

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

This is a well-structured TypeScript MCP server with 4 tools for Tolk smart contract compilation. All tools are properly registered with names, descriptions, and input schemas using Zod. Naming follows verb_noun conventions (get_, compile_, check_, generate_). Descriptions are substantial and explain the purpose, use case, and output. Input schemas use proper type constraints with min/max bounds. However, output schemas are not formally documented, responses are returned as text content without a declared schema structure. Error handling is basic (returns isError flag with text message). The server lacks several optional MCP features (logging, sampling, elicitation, roots, cancellation, progress, tool annotations). Transport is STDIO only, which applies a hard cap at 50 for protocol readiness.

Tools (4)

check_tolk_syntaxread onlysource verified

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.

compile_tolkread onlysource verified

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.

generate_deploy_linkread onlysource verified

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.

get_compiler_versionread onlysource verified

Returns the version of the Tolk compiler (from @ton/tolk-js WASM). Use this to check which compiler version is available.

Issues (4)

HIGHresponse-shaper ↗

Output schemas are not formally documented. Tools return text content via MCP's content array, but the structured fields in the response (code hash, BoC, Fift code) are not declared in an output schema. This forces LLMs to parse unstructured markdown text to extract downstream dependencies.

compile_tolkcheck_tolk_syntaxgenerate_deploy_link

HIGHrecovery-guide ↗

Error handling is generic. Errors return a text message with isError=true flag. There is no error categorization (retryable vs fatal), no recovery guidance, and no structured error codes per MCP spec. E.g., compilation errors and validation errors return the same isError response format.

compile_tolkcheck_tolk_syntax

MEDIUMperformance-hint ↗

Missing optional MCP features: no tool annotations (readOnlyHint, destructiveHint, idempotentHint). All tools are read-only and idempotent, but these hints are not declared. This prevents MCP clients from optimizing execution (e.g., caching, parallel execution, retry strategies).

get_compiler_version

Recommendations

Define an explicit output schema for compile_tolk showing fields like code_hash (string), boc_base64 (string), fift_code (string), boc_size_bytes (number). Return structured JSON instead of markdown-formatted text content. This lets LLMs reliably extract and chain outputs.
Implement structured error responses with error codes (e.g., VALIDATION_ERROR, COMPILATION_ERROR, FILE_NOT_FOUND). Include recovery guidance: 'Total sources size exceeded 1MB. Reduce file size or split into smaller contracts.' Categorize errors as retryable or user-fixable.
Add tool annotations via MCP's InputSchema extension. Mark all tools with readOnlyHint=true and idempotentHint=true so clients can safely cache results and retry safely.
Migrate from STDIO to HTTP transport. Use a simple Express or Node HTTP server that wraps the MCP protocol. This enables remote access, testing via HTTP clients, and integration with hosted MCP platforms.
Add a dry_run parameter to generate_deploy_link (optional boolean, default false) to let agents preview the deployment without committing. This follows the confirmation-request pattern for potentially destructive operations.
Document output schemas in tool descriptions. E.g., 'Returns: {code_hash: string, boc_base64: string, fift_code: string}' so agents know what fields to expect.
Add pagination/limits for potential future tools. The sources parameter accepts up to 50 files and 1MB total, document these limits in the description and return a summary of applied constraints in the response.

Score history

Overall score trend

↓ 41 points across a rubric change (v1 → v2)

11/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-22	F	11	2026-07-28+	v2
2026-03-09	D	52	-	v1