citadelle-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RPC_URL | No | Your EVM RPC endpoint (default: https://rpc.testnet.chain.robinhood.com) | https://rpc.testnet.chain.robinhood.com |
| WEB_UI_BASE_URL | No | The domain of the Citadelle Web UI for trade links (default: https://citadelle.com) | https://citadelle.com |
| CONTRACT_ADDRESS | No | The EVM address of the Citadelle Options smart contract |
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 |
|---|---|
| get_markets_liquidityA | Fetches all Citadelle options markets directly from the EVM blockchain and filters them by available liquidity. |
| get_wallet_portfolioA | Fetches open Citadelle options positions for a specific EVM wallet directly from the blockchain. |
| generate_trade_linkA | Generates a URL that redirects the user to the web UI to securely execute an option trade. |
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 clearly distinct concern: market liquidity, wallet positions, and trade execution. There is no overlap or plausible confusion between them.
Two tools follow the get_verb_noun pattern and the third uses generate_trade_link, which is a natural and consistent extension of the same verb-object style. All names are in snake_case with clear, readable intent.
Three tools is within the ideal range and each serves a necessary step in the user journey: viewing markets, checking portfolio, and initiating a trade. The scope is compact but well-defined.
The tool set covers the core flow of discovering markets, reviewing positions, and generating a trade link, which is sufficient for most read-and-execute workflows. Minor gaps like fetching individual position details or market history exist but do not create dead ends.