Get block information from the Klever blockchain by nonce (block number). If no nonce is provided, returns the latest block. Returns hash, timestamp, proposer, number of transactions, and other block metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| nonce | No | Block number (nonce). Omit to get the latest block. | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already signal a safe, read-only, idempotent operation. The description adds value by specifying the returned fields (hash, timestamp, proposer, transaction count) and the latest-block behavior, which are not covered by annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the main action and resource. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with two optional parameters and no output schema, the description covers the purpose, return payload, and parameter behavior sufficiently. It's complete for the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so parameters are well-documented. The description adds further clarification for the nonce parameter by explaining the behavior when omitted, and the network parameter is already fully described in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function—retrieving block information from the Klever blockchain—and identifies the distinguishing resource (block by nonce) and optional latest-block behavior. This sets it apart from sibling tools like get_transaction or get_account, which target other entities.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear context on when to use the tool (need block info, optionally by nonce) and explains the fallback to the latest block when nonce is omitted. However, it doesn't explicitly mention alternatives or when not to use it, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.
