Capital Flow Desk — UnlockFlow MCP
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 |
|---|---|
| list_unlock_eventsA | List local UnlockFlowEvent v1 samples (illustrative). Optional filters: asset ticker, horizon. Seeds have illustrative:true — NFA, not live Agent Feed. Live feed: @CapitalFlowDeskBot / @Mohammad_GNA (99/299 USDT TRC-20). |
| get_unlock_eventA | Fetch one UnlockFlowEvent by event_id from local illustrative seeds. |
| get_schemaA | Return UnlockFlowEvent JSON Schema v1 (schema_version "1"). |
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 has a distinct purpose: listing events, fetching a single event by ID, and retrieving the schema. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: list_unlock_events, get_unlock_event, and get_schema. The naming is predictable and easy to infer.
Three tools is appropriate for a server scoped to illustrative local samples. Each tool earns its place: list, get, and schema introspection.
For the stated purpose of accessing local illustrative UnlockFlowEvent v1 samples, the surface is complete: list, fetch by ID, and schema retrieval cover all necessary read-only operations. Live feed and mutation tools are explicitly out of scope.