Skip to main content
Glama

mcp-klever-vm

by io.github.klever-io

init_klever_project

Read-onlyIdempotent

Scaffold a new Klever smart contract project using the SDK. Creates the Rust project structure via ksc new and generates automation scripts (build, deploy, upgrade, query, test, interact). Requires Klever SDK installed at ~/klever-sdk/. Run check_sdk_status first to verify. NOTE: In public profile, this tool returns a project template JSON and does not perform any filesystem changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe contract project name in kebab-case (e.g. "my-token", "nft-marketplace"). Used as the Cargo package name and directory name.
noMoveNoWhen true, keeps the project in the SDK output directory instead of moving it to the current working directory. Default: false.
templateNoProject template to scaffold from. "empty" creates a blank contract with just an init function. "adder" creates a simple counter example. Default: "empty".empty

TDQS

A3.6/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true, but the description states 'Creates the Rust project structure' and 'generates automation scripts', which implies filesystem modifications. A note about public-profile behavior does not resolve the contradiction for the default profile, as the main description directly contradicts the read-only annotation. This is an annotation contradiction.

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 compact and front-loaded with the main purpose, then provides the exact command, generated outputs, prerequisites, and a crucial behavioral note about public profile. Every sentence adds value with no redundancy.

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?

Covers purpose, generated scripts, SDK requirement, prerequisite verification, and public-profile behavior. With all parameters fully described in the schema and no output schema, the description is nearly complete, though the ambiguity around default side effects is handled under transparency.

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

Parameters3/5

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

Schema description coverage is 100%, and parameter descriptions for name, noMove, and template are already self-sufficient. The tool description adds no parameter-specific details, but given the high schema coverage, the baseline of 3 is appropriate.

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?

Description uses a specific verb 'Scaffold' with a clear resource 'new Klever smart contract project', and explicitly mentions the underlying command `ksc new` and generated automation scripts. This distinguishes it from sibling tools like add_helper_scripts by emphasizing creation of a new project.

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?

Provides explicit prerequisites: requires the Klever SDK at ~/klever-sdk/ and instructs to run check_sdk_status first. This gives clear context for when to use the tool, though it doesn't explicitly state when not to use it or name alternative tools.

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

All mcp-klever-vm toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, such as get_balance for token balances, analyze_contract for code analysis, and init_klever_project for project scaffolding. However, there is some overlap between query_context and search_documentation, both of which search the knowledge base, which could cause confusion about which to use for specific queries.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern throughout, such as get_balance, analyze_contract, and init_klever_project. Minor deviations exist, like add_helper_scripts (verb_adjective_noun) and enhance_with_context (verb_preposition_noun), but overall, the pattern is clear and predictable.

Tool Count4/5

With 16 tools, the count is slightly high but reasonable for the Klever VM domain, which covers blockchain queries, smart contract development, and knowledge base management. It provides comprehensive coverage without being overwhelmingly large, though it could be streamlined by merging overlapping tools.

Completeness5/5

The tool set offers complete coverage for Klever VM development, including project setup (init_klever_project, add_helper_scripts), contract analysis and querying (analyze_contract, query_sc), blockchain data retrieval (get_balance, get_transaction, get_block), and knowledge base access (query_context, search_documentation). No obvious gaps are present for the intended scope.

Resources