robinhood-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 |
|---|---|
| get_setup_statusA | Report why this Robinhood server has no working credentials and what to set. Every other tool is unavailable until credentials are configured, so call this first if no trading or market-data tools are listed. |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly distinct: it reports setup status.
The single tool name 'get_setup_status' follows a clear verb_noun pattern, consistent with common MCP naming conventions. No inconsistencies are possible with only one tool.
A single setup-status tool is an extreme mismatch for a server named 'robinhood-mcp', which implies a full trading/market-data toolset. The description even acknowledges that other tools would exist but are unavailable, making the current surface trivially thin.
The server's apparent domain is Robinhood trading, but the only tool provides setup status and no actual trading or market data operations. This is severely incomplete and provides no way to accomplish any real task.