Vitruveo Chain Tools MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chain_statusA | Verify chain ID, RPC health, and current block. |
| address_overviewC | Native VTRU balance, contract status, explorer metadata including NFTs and proxy info. |
| block_detailsC | Read a block by number or latest. |
| transaction_detailsB | Read transaction, receipt and Blockscout decoding by transaction hash. |
| address_history_pageB | Read one Blockscout page with exact pagination cursor (transactions, logs, transfers, token holdings, internal transactions). |
| read_contractB | Call any ABI-described view or pure method on an arbitrary contract, including proxies. No wallet signing. |
| decode_event_logsB | Decode raw event log entries with a supplied Solidity event signature. |
| scan_address_transactionsC | Paginate public address incoming/outgoing transactions, group decoded methods, optionally sum uint quantity for one method, and flag incomplete runs. NOT proof of sales. |
| native_balanceC | Native VTRU balance at a pinned block. |
| token_infoC | Read ERC-20 interface information and optional holder balance. |
| nft_infoB | Read ERC-721 ownership and URI without fetching external metadata. |
| contract_inspectC | Observe bytecode, EIP-1967 proxy slots and explorer ABI metadata. |
| contract_logsC | Read at most 2000 blocks and 500 log records; explicit completeness. |
| validator_observationsC | Sample block author fields; not proof of validator membership. |
| reconcile_supplyC | Read caller-selected cap/outstanding/reserved getters at one block; never a paid-sales total. |
| historical_availabilityC | Point probes of historical block and state; never proof of complete archive coverage. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Several tools overlap: address_overview and native_balance both return native balance, address_history_page and scan_address_transactions both traverse address transactions, and contract_logs/decode_event_logs/historical_availability all touch logs or historical state. Descriptions add caveats and pinned-block distinctions, but an agent must read carefully to choose correctly.
All names use snake_case, which is consistent, but the convention is split between noun phrases (chain_status, block_details, token_info) and verb phrases (read_contract, decode_event_logs, scan_address_transactions). The mixed style remains readable but is not a single predictable pattern.
16 tools is slightly above the typical 3-15 range but reasonable for a read-only chain inspection and analysis surface. Each tool maps to a specific query type, though a few overlaps suggest some could be consolidated.
The surface covers core read-only chain workflows: status, blocks, transactions, addresses, contracts, logs, tokens, NFTs, validators, supply reconciliation, and historical probes. Minor gaps remain around gas estimation, broad event/topic filtering, and richer token/NFT enumeration, but no major dead ends for the stated purpose.