mcp-server-ddd-template
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 |
|---|---|
| get-recommended-feesB | Get recommended fees for Bitcoin |
| get-pingA | Get ping to check service is working |
| get-blockA | Returns details about a block from hash |
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 targets a distinct purpose: block details, health check, and fee recommendations. There is no overlap or ambiguity.
All tools follow a consistent 'get-' prefix with hyphenated lowercase naming, forming a clear pattern.
Three tools is a reasonable count for a minimal Bitcoin service, though the server's purpose as a template might justify even fewer.
The set covers block retrieval, health checking, and fee recommendations, but lacks common Bitcoin operations like transaction handling, making it somewhat incomplete for a full service.