Sandcastle MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROBINHOOD_RPC_URL | No | Optional override for the Robinhood Chain JSON-RPC endpoint. If not set, a default public RPC is used. | |
| SANDCASTLE_SUBGRAPH_URL | No | Optional override for the Sandcastle subgraph GraphQL endpoint. If not set, the default public subgraph is used. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_marketsA | List the curated Sandcastle leveraged-liquidity markets and their deployment addresses. |
| get_marketA | Read a Sandcastle market, its Uniswap V3 pool, and stored Morpho totals from Robinhood Chain. Accepts a market id, pool address, or Morpho market id. |
| get_positionsA | Discover an owner’s Position Accounts through the Sandcastle subgraph, then read active NFT, pool, Morpho debt, oracle collateral value, equity, leverage, and health from chain. |
| simulate_payoffB | Project equity and return on equity for a concentrated-liquidity position across terminal prices. Quote debt stays fixed in USD; base debt changes with the base price. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| sandcastle-deployments | Curated Sandcastle contracts and markets used by this server. |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: listing markets, reading a specific market's details, discovering and reading positions, and simulating payoff scenarios. No overlaps in functionality.
All tool names follow a consistent verb_noun pattern (list_markets, get_market, get_positions, simulate_payoff) with clear, predictable verbs and nouns.
With 4 tools, the server is well-scoped for its purpose of reading markets and positions and simulating outcomes. Slightly lean but each tool is substantial.
The tools cover the main read paths and a simulation, but lack actions like creating positions or managing them. Given the read-focused nature, this is a minor gap.