Skip to main content
Glama
Sign In
Vitruveo Chain Tools MCP

Vitruveo Chain Tools MCP

by UNI-ASYNC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

native balance

native_balance
Read-only

Retrieves the native VTRU balance for a 0x address at the latest block or a pinned block number, supporting historical balance checks.

Instructions

Native VTRU balance at a pinned block.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "native_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
blockNumberNolatest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0-rc.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description's only added behavioral nuance is 'pinned block', which weakly signals that results can be a historical snapshot, but it says nothing about units/decimals of the returned balance, whether 'latest' is the default, or how pending blocks are treated.

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

Conciseness3/5

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

The single short fragment is front-loaded and free of padding, which is good, but it is undersized for a two-parameter tool rather than genuinely concise. It reads more like a title restatement than a useful sentence.

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

Completeness3/5

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

Annotations carry the read-only/safe profile and there is no output schema to explain, so the baseline is low. Still, with 0% schema coverage the description leaves both parameters and the meaning of the returned native balance (units, decimals, historical vs latest semantics) undocumented.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and does not. The required 'address' parameter is never mentioned, and 'pinned block' only vaguely gestures at 'blockNumber' without explaining that it accepts 'latest' or a decimal string — the agent has to read the anyOf/const/default in the raw schema.

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

Purpose3/5

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

The fragment 'Native VTRU balance' identifies a recognizable resource (the chain's native token balance) and 'at a pinned block' hints at the block scoping, but there is no verb and no explicit statement that this is a read of an address's balance. Sibling differentiation is only implicit — an agent must infer this differs from address_overview or token_info, which likely report broader or token-level holdings.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives such as address_overview (multi-asset overview) or token_info (non-native tokens). The agent gets no rule for choosing this tool over its siblings.

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

Deploy Server

Other Tools