Skip to main content
Glama

get_compiler_version

Retrieve the version of the Tolk compiler. Use this to confirm which compiler version is available.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.ts:51-72 (registration)
    Registers the 'get_compiler_version' tool on the MCP server with an empty schema; calls getTolkCompilerVersion() from @ton/tolk-js to return the compiler version.
    export function registerTools(server: McpServer): void {
      // ─── Tool 1: get_compiler_version ───────────────────────────────
    
      server.tool(
        "get_compiler_version",
        "Returns the version of the Tolk compiler (from @ton/tolk-js WASM). " +
          "Use this to check which compiler version is available.",
        {},
        async () => {
          try {
            const version = await getTolkCompilerVersion();
            return {
              content: [{ type: "text", text: `Tolk compiler version: ${version}` }],
            };
          } catch (err) {
            return {
              content: [{ type: "text", text: `Failed to get compiler version: ${getErrorMessage(err)}` }],
              isError: true,
            };
          }
        },
      );
  • Async handler function that awaits getTolkCompilerVersion() from @ton/tolk-js and returns the version string, with error handling.
    async () => {
      try {
        const version = await getTolkCompilerVersion();
        return {
          content: [{ type: "text", text: `Tolk compiler version: ${version}` }],
        };
      } catch (err) {
        return {
          content: [{ type: "text", text: `Failed to get compiler version: ${getErrorMessage(err)}` }],
          isError: true,
        };
      }
    },
  • Empty input schema object ({}) for get_compiler_version, as the tool takes no arguments.
    {},
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose all behavioral traits. It states the tool returns version information, implying a read-only operation, but does not explicitly confirm no side effects or other behaviors. Given the trivial nature, this is borderline adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: one sentence that conveys purpose and usage context with no filler or redundancy. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no parameters and a simple return (version string), the description is complete enough to inform usage. It does not detail the exact format of the version string, but that is implicit and acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so schema coverage is 100%. The baseline for 0 parameters is 4, and the description adds no parameter info because none exist. No deduction needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns the compiler version, using a specific verb 'Returns' and specifies the resource 'Tolk compiler version'. It distinguishes from sibling tools (syntax check, compile, deploy link) by focusing on version retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises using this tool 'to check which compiler version is available', providing clear context. However, it does not mention when not to use it or suggest alternatives, which would strengthen guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/izzzzzi/izTolkMcp'

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