actually-mcp-server
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 |
|---|---|
| check_newsA | Map a piece of news text to the relevant Polymarket market and return its objective YES probability. Does not classify whether the news is dramatized or accurate relative to the market - that interpretation is left to the calling agent, which has both the original text and this market anchor. The probability comes from a precomputed cache refreshed on a cron cadence (can be up to ~2 hours stale) - for a live price before trading, call get_market with the returned marketId. |
| get_marketA | Look up a specific Polymarket market by id: details, live price, and an orderbook snapshot. Falls back to a direct Gamma lookup when the id is outside the precomputed cache's top markets by volume. |
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 2 tools
check_news takes natural language news text and returns a market anchor with a cached YES probability, while get_market requires a specific marketId and returns live market and orderbook data. The input types and outputs are distinct, and the description explicitly frames them as complementary rather than overlapping.
Both tool names follow the same snake_case verb_noun pattern: check_news and get_market. The verbs are simple and descriptive, with no mixed conventions or inconsistent styling.
Two tools is lean, but the server appears intentionally narrow: it maps news to a Polymarket market and provides live market data. Both tools are necessary for that workflow, making the count slightly small but still reasonable.
For the stated purpose, the tool surface is complete: check_news handles the news-to-market mapping, and get_market provides the live price and orderbook follow-up referenced by check_news. The primary workflow has no obvious dead ends.