Mina Archive Node
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query-actionsC | Query actions from the Mina blockchain with optional filters |
| query-eventsC | Query events from the Mina blockchain with optional filters |
| get-network-stateB | Get the current state of the Mina network |
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 3 tools
Each tool has a clearly distinct purpose: get-network-state retrieves the current network state, query-actions handles blockchain actions with filters, and query-events handles blockchain events with filters. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern with hyphens: get-network-state, query-actions, and query-events. The naming is uniform and predictable throughout the set.
With only 3 tools, the count feels thin for an archive node that might need more comprehensive blockchain interaction capabilities. While the tools cover basic queries and network state, it's borderline minimal for the apparent scope.
The tools provide core querying functions (network state, actions, events), but there are notable gaps such as missing data submission tools (e.g., for transactions or smart contracts) and advanced analytical operations. This could limit agent workflows in a blockchain context.