@pmxt/mcp 2.30.9 → 2.31.1

package/dist/generated/tools.js

@@ -1,5 +1,5 @@
 // AUTO-GENERATED by mcp/scripts/generate-tools.js -- DO NOT EDIT
-// Generated from core/src/server/openapi.yaml (2026-04-14)
+// Generated from core/src/server/openapi.yaml (2026-04-18)
 export const TOOLS = [
     {
         "name": "buildOrder",
@@ -654,6 +654,25 @@ export const TOOLS = [
                     "type": "string",
                     "description": "Lookup by event slug"
                 },
+                "filter": {
+                    "allOf": [
+                        {
+                            "$ref": "#/components/schemas/EventFilterCriteria"
+                        }
+                    ],
+                    "description": "Optional client-side filter applied after fetching"
+                },
+                "category": {
+                    "type": "string",
+                    "description": "Shorthand for filter.category -- merged into filter (takes precedence)"
+                },
+                "tags": {
+                    "type": "array",
+                    "items": {
+                        "type": "string"
+                    },
+                    "description": "Shorthand for filter.tags -- merged into filter (takes precedence)"
+                },
                 "verbose": {
                     "type": "boolean",
                     "description": "Return full uncompacted response. Default false returns a compact, agent-friendly summary."
@@ -678,7 +697,7 @@ export const TOOLS = [
     },
     {
         "name": "fetchEvents",
-        "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.",
+        "description": "Fetch events with optional keyword search. Events group related markets together (e.g., \"Who will be Fed Chair?\" contains multiple candidate markets).",
         "inputSchema": {
             "type": "object",
             "properties": {
@@ -747,6 +766,25 @@ export const TOOLS = [
                     "type": "string",
                     "description": "Lookup by event slug"
                 },
+                "filter": {
+                    "allOf": [
+                        {
+                            "$ref": "#/components/schemas/EventFilterCriteria"
+                        }
+                    ],
+                    "description": "Optional client-side filter applied after fetching"
+                },
+                "category": {
+                    "type": "string",
+                    "description": "Shorthand for filter.category -- merged into filter (takes precedence)"
+                },
+                "tags": {
+                    "type": "array",
+                    "items": {
+                        "type": "string"
+                    },
+                    "description": "Shorthand for filter.tags -- merged into filter (takes precedence)"
+                },
                 "verbose": {
                     "type": "boolean",
                     "description": "Return full uncompacted response. Default false returns a compact, agent-friendly summary."
@@ -880,7 +918,7 @@ export const TOOLS = [
     },
     {
         "name": "fetchMarkets",
-        "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.",
+        "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.",
         "inputSchema": {
             "type": "object",
             "properties": {
@@ -1016,6 +1054,9 @@ export const TOOLS = [
                 "cursor": {
                     "type": "string"
                 },
+                "filter": {
+                    "$ref": "#/components/schemas/MarketFilterCriteria"
+                },
                 "verbose": {
                     "type": "boolean",
                     "description": "Return full uncompacted response. Default false returns a compact, agent-friendly summary."

package/package.json

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