Lucho Treasury
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lucho_plan_treasuryB | Calculate protected liquidity, score normalized Binance earning products, stress-test the proposed allocation, and return ALLOCATE, HOLD, or BLOCK. This tool never executes a financial action. |
| lucho_tighten_planB | Apply a critic decision that may only reduce allocations or veto products. It cannot increase the deterministic plan. |
| lucho_verify_stressB | Re-run mandatory liquidity and rate-drop stress checks for a proposed plan. This tool never executes a financial action. |
| lucho_create_receiptA | Create a fingerprinted, credential-safe receipt for a completed fixture, dry-run, or live decision. This does not execute the plan. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| put-idle-money-to-work | Orchestrate Binance Agent OS reads with Lucho Treasury planning while protecting stated liabilities and requiring action-specific confirmation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
plan_treasury and verify_stress both involve stress-testing a proposed allocation, so an agent could confuse them; however, plan_treasury returns a broad decision while verify_stress is a focused re-check, and tighten_plan and create_receipt are clearly distinct.
All tools share the lucho_ prefix and follow a snake_case verb_noun structure: tighten_plan, plan_treasury, verify_stress, create_receipt. There is no mixing of casing or verb styles.
Four tools is well-scoped for a narrowly focused treasury decision-support server. Each tool covers a distinct phase of the workflow without unnecessary bloat.
The core lifecycle is covered: plan, stress-verify, tighten, and create a receipt. Execution is deliberately out of scope, but minor gaps exist around viewing or explicitly proposing an initial allocation.