prediction-market-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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-prediction-marketsC | Get prediction market prices from Polymarket, PredictIt, and Kalshi |
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
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined to fetch prediction market prices from specific sources.
Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate. The tool name follows a clear verb_noun pattern (get-prediction-markets).
A single tool is too few for a server named 'prediction-market-mcp', which suggests a broader domain involving prediction markets. This minimal toolset limits functionality and likely leaves significant gaps in coverage, such as creating markets, placing bets, or managing accounts.
The tool surface is severely incomplete for the prediction market domain. It only provides a read operation (get prices) but lacks essential CRUD/lifecycle operations like creating markets, updating positions, or deleting entries, which are critical for agent workflows in this context.