dd-explain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOW_NETWORK | No | Set to '1' to enable live network access via digiexplorer.info. Defaults to '0' (off), using only bundled fixtures. | 0 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| explain_digidollar_txA | Explain a DigiDollar transaction recorded in DigiByte from its txid. Resolution is fixture-first: offline fixtures/TXID.json is preferred; live digiexplorer.info only when ALLOW_NETWORK=1. The response source field labels fixture vs digiexplorer — agents must not treat a fixture as live chain state. Classifies via consensus type byte; returns kind, amounts (cents/USD), ddOutputs, burns if redeem (burn = consumed − change via one-hop valuation of creating txs when reachable), collateralSpends count, shapeOk, block height/time if present, and disclaimer fields. Read-only. Facts and hashes only; inferences marked Unverified. Product name: DigiDollar transaction explainer (dd-explain-mcp). Lookup UI: https://dgbinsights.com/lookup |
| decode_dd_opreturnA | Offline decode of a DigiDollar OP_RETURN scriptPubKey hex via parseDDOpReturn. Returns consensus type byte kind (mint/transfer/redeem), amounts in cents, and fields. No network. Read-only. Does not label entities. |
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 2 tools
The two tools take entirely different inputs (a txid vs. OP_RETURN hex) and serve distinct purposes: high-level transaction explanation versus low-level script decoding. Their descriptions clearly delineate when each should be used, leaving no ambiguity.
Both tools follow the same verb_noun snake_case pattern: explain_digidollar_tx and decode_dd_opreturn. The verbs accurately describe the action and the nouns specify the target, making the naming predictable and consistent.
With only two tools, the server feels thin even though its purpose is narrowly focused on explaining DigiDollar transactions. The count is borderline but acceptable for such a specialized utility; it is not excessive but also not richly scoped.
The tool surface covers the essential workflows for its domain: full transaction explanation and offline OP_RETURN decoding. Minor gaps exist, such as no support for raw full-transaction hex decoding, but the core explainer and decoder are sufficient for most use cases.