W3 Ledger MCP Server
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 |
|---|---|
| check_balanceA | Check the token balances (DAH, DAHYM, DAHLOR, W3SH) for a public key. Returns total balance, per-token breakdown, maturity info, merchant breakdown, and W3SH loyalty tier (Seed/Twig/Kindling/Log/Joist) with cashback rate and progress. |
| create_gift_cardA | Create a gift card by debiting the customer's DAH balance. Requires dual signatures (customer + distribution). The card value is escrowed until the recipient claims it. |
| claim_gift_cardA | Claim a gift card and credit the claimer's DAH balance. Only cards with status ISSUED can be claimed. |
| create_sponsor_cardA | Create a location-based sponsor card by debiting the sponsor's DAH balance. Requires dual signatures. The card can be claimed by users near the sponsor location. |
| claim_sponsor_cardA | Claim a sponsor card and credit the claimer's DAH balance. Only cards with status ISSUED can be claimed. |
| purchase_productA | Purchase a product by debiting the sender's DAH balance and crediting the receiver (merchant). Requires dual signatures. |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: check_balance for viewing balances, claim_gift_card and claim_sponsor_card for claiming different card types, create_gift_card and create_sponsor_card for creating different card types, and purchase_product for product transactions. The descriptions specify unique actions and contexts, making misselection unlikely.
All tool names follow a consistent verb_noun pattern (e.g., check_balance, claim_gift_card, create_sponsor_card) with clear, descriptive terms. There are no deviations in style or convention, making the set predictable and easy to understand.
With 6 tools, the server is well-scoped for its ledger and token management domain. Each tool serves a specific, necessary function (balance checking, card creation/claiming, and product purchases), and none feel redundant or missing, fitting typical tool counts for such a purpose.
The tool set covers core operations for token balances, gift/sponsor card lifecycle, and product purchases, with clear CRUD-like actions (create/claim for cards, check for balances, purchase for transactions). A minor gap exists in lacking update or delete operations for cards or balances, but agents can likely work around this given the escrow and dual-signature constraints described.