@pmxt/mcp 2.30.1 → 2.30.2

package/dist/generated/tools.js

@@ -650,7 +650,7 @@ export const TOOLS = [
     },
     {
         "name": "fetchEvents",
-        "description": "Fetch events with optional keyword search. Events group related markets together (e.g., \"Who will be Fed Chair?\" contains multiple candidate markets).",
+        "description": "Start here for discovery and search. Events are the top-level grouping in the data model: Event -> Market -> Outcome. An event is a broad topic (e.g., \"Who will win the 2028 presidential election?\"), a market is a specific tradeable question within that event (e.g., \"Will Kamala Harris win the 2028 presidential election?\"), and an outcome is the side you buy (e.g., \"Yes\" or \"No\"). When a user asks to \"find\", \"search for\", or \"look up\" a market, use this tool — they almost always mean the event-level topic. Each returned event includes its child markets. Supports optional keyword search, filtering, and pagination.",
         "inputSchema": {
             "type": "object",
             "properties": {
@@ -844,7 +844,7 @@ export const TOOLS = [
     },
     {
         "name": "fetchMarkets",
-        "description": "Fetch markets with optional filtering, search, or slug lookup. Always hits the exchange API — results reflect the live state at the time of the call.",
+        "description": "Fetch individual tradeable contracts (markets). A market is a specific question like \"Will Kamala Harris win the 2028 presidential election?\" — for general discovery or search, prefer fetchEvents instead, which returns the higher-level topic (e.g., \"Who will win the 2028 presidential election?\") with all its markets grouped together. When users say \"search for a market\" they almost always mean an event. Use fetchMarkets when you need a specific contract by ID/slug, or when you already have an eventId and want its child markets. Always hits the exchange API — results reflect the live state at the time of the call.",
         "inputSchema": {
             "type": "object",
             "properties": {

package/dist/server.js

@@ -14,6 +14,12 @@ Same methods, same response shape, regardless of venue.
 
 SETUP: Get an API key at pmxt.dev/dashboard. Set PMXT_API_KEY in your environment.
 
+DATA MODEL (Event -> Market -> Outcome):
+- Event: a broad topic, e.g. "Who will win the 2028 presidential election?"
+- Market: a specific tradeable question within an event, e.g. "Will Kamala Harris win the 2028 presidential election?"
+- Outcome: the side you buy or sell, e.g. "Yes" (she wins) or "No" (she does not win).
+When users say "market" they almost always mean an event. Use fetchEvents for discovery and search.
+
 IMPORTANT RULES:
 - NEVER place orders (createOrder, submitOrder) without explicit user confirmation. \
 These spend real money. Always show the user the order details (venue, market, side, price, amount) and wait for approval.
@@ -22,10 +28,12 @@ These spend real money. Always show the user the order details (venue, market, s
 - Venue credentials (privateKey, apiKey) are sensitive. Never log or display them.
 
 WORKFLOW:
-1. Use fetchMarkets or fetchEvents to discover markets (use the "query" param for search).
-2. Use fetchOrderBook to check liquidity and prices.
-3. Use getExecutionPrice to quote a trade before placing it.
-4. Use buildOrder to preview, then submitOrder to execute (with user approval).
+1. Use fetchEvents to discover and search for topics (use the "query" param). This is the right starting point \
+even when the user says "market" -- they almost always mean an event. Each event includes its child markets.
+2. Use fetchMarkets only when you need a specific contract by ID/slug, or to list markets within a known event.
+3. Use fetchOrderBook to check liquidity and prices.
+4. Use getExecutionPrice to quote a trade before placing it.
+5. Use buildOrder to preview, then submitOrder to execute (with user approval).
 
 The "exchange" param is required on every call. Options: polymarket, kalshi, limitless, probable, etc.`;
 export function createServer(config) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pmxt/mcp",
-  "version": "2.30.1",
+  "version": "2.30.2",
   "description": "MCP server for PMXT - the unified prediction market API",
   "type": "module",
   "bin": {