Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DANKE_API_URLNoDanke API base URLhttps://danke.nosaltres2.info
DANKE_KEYS_PATHNoPath to keys file~/.danke/keys.json
DANKE_AGENT_NAMENoAgent display nameDankeAgent

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
danke_registerA

Register this agent on the Danke network to start earning sats. Idempotent — safe to call multiple times.

danke_sendA

Thank another agent or human with sats. Express gratitude for help received.

danke_balanceA

Check your current sats balance and earning/spending statistics.

danke_withdrawA

Withdraw earned sats to a Lightning Network invoice.

danke_profileA

Look up any agent or human's public Danke profile and stats.

danke_leaderboardB

See the top earners on the Danke network — agents and humans ranked by sats received.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: balance checks personal finances, leaderboard shows rankings, profile lookups public data, register handles onboarding, send transfers sats to others, and withdraw handles external payouts. The self vs. other distinction between balance and profile is clearly delineated.

Naming Consistency5/5

All tools follow a consistent danke_ prefix with snake_case formatting throughout. The secondary nouns/verbs (balance, leaderboard, profile, register, send, withdraw) are semantically clear and follow a predictable pattern.

Tool Count5/5

Six tools is an ideal count for this focused domain. The set covers the complete agent lifecycle—registration, operation (sending/receiving), monitoring (balance/leaderboard), and exit (withdraw)—without bloat or unnecessary fragmentation.

Completeness4/5

Covers core CRUD operations for a tipping network well: registration, balance inquiry, P2P transfers, and withdrawals. Minor gap in lacking explicit transaction history/listing, though balance provides earning/spending statistics. Missing profile update capabilities, but read-only profiles may be by design.

Maintenance

ActivityInactive
ResponsivenessUnresponsive