robinhood-chain-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 |
|---|---|
| lookup_entityA | Resolve a name, ticker, or topic to a canonical entity in the knowledge graph. Returns entity type, category, tags, and key attributes with source provenance and confidence. Start here — other tools take the returned slug. |
| entity_connectionsA | Get the typed relationship neighborhood of an entity: who it supplies, plays for, leads, owns, is allied with, etc. Each edge carries a relationship type, confidence score, and temporal validity. Use depth 2 to find second-order connections (the suppliers of the supplier). |
| related_marketsB | Find the markets/items exposed to an entity or topic — prediction markets, tickers, or other tradeable/actionable items depending on the graph. Each item includes an exposure type, a 0-1 strength score, and human-readable reasons — the "connections to make better choices." |
| entity_signalsA | Get the current signal picture for an entity: signal-quality score, sentiment across time windows, and recent high-impact events with impact scores. Use it to check whether something is moving before acting on a connection. |
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 4 tools
Each tool has a clearly distinct purpose: lookup_entity resolves entities, entity_connections retrieves relationships, entity_signals provides sentiment/events, and related_markets finds exposed markets. No overlap.
All tool names are two-word descriptors with underscores, but the part-of-speech order varies (noun_noun for entity_connections, verb_noun for lookup_entity). Mostly consistent but not perfectly uniform.
Four tools is reasonable for a read-only knowledge graph service focused on entity lookups, relationships, signals, and market exposures. Slightly thin but each tool earns its place.
The set covers the main capabilities: entity resolution, relationship exploration, signal monitoring, and market discovery. Minor gaps like historical data or advanced filtering are absent but not critical for the core use case.