@pmxt/mcp 2.30.8 → 2.31.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -654,6 +654,14 @@ export const TOOLS = [
654
654
  "type": "string",
655
655
  "description": "Lookup by event slug"
656
656
  },
657
+ "filter": {
658
+ "allOf": [
659
+ {
660
+ "$ref": "#/components/schemas/EventFilterCriteria"
661
+ }
662
+ ],
663
+ "description": "Optional client-side filter applied after fetching"
664
+ },
657
665
  "verbose": {
658
666
  "type": "boolean",
659
667
  "description": "Return full uncompacted response. Default false returns a compact, agent-friendly summary."
@@ -678,7 +686,7 @@ export const TOOLS = [
678
686
  },
679
687
  {
680
688
  "name": "fetchEvents",
681
- "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.",
689
+ "description": "Fetch events with optional keyword search. Events group related markets together (e.g., \"Who will be Fed Chair?\" contains multiple candidate markets).",
682
690
  "inputSchema": {
683
691
  "type": "object",
684
692
  "properties": {
@@ -747,6 +755,14 @@ export const TOOLS = [
747
755
  "type": "string",
748
756
  "description": "Lookup by event slug"
749
757
  },
758
+ "filter": {
759
+ "allOf": [
760
+ {
761
+ "$ref": "#/components/schemas/EventFilterCriteria"
762
+ }
763
+ ],
764
+ "description": "Optional client-side filter applied after fetching"
765
+ },
750
766
  "verbose": {
751
767
  "type": "boolean",
752
768
  "description": "Return full uncompacted response. Default false returns a compact, agent-friendly summary."
@@ -880,7 +896,7 @@ export const TOOLS = [
880
896
  },
881
897
  {
882
898
  "name": "fetchMarkets",
883
- "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.",
899
+ "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.",
884
900
  "inputSchema": {
885
901
  "type": "object",
886
902
  "properties": {
@@ -1016,6 +1032,9 @@ export const TOOLS = [
1016
1032
  "cursor": {
1017
1033
  "type": "string"
1018
1034
  },
1035
+ "filter": {
1036
+ "$ref": "#/components/schemas/MarketFilterCriteria"
1037
+ },
1019
1038
  "verbose": {
1020
1039
  "type": "boolean",
1021
1040
  "description": "Return full uncompacted response. Default false returns a compact, agent-friendly summary."
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pmxt/mcp",
3
- "version": "2.30.8",
3
+ "version": "2.31.0",
4
4
  "description": "MCP server for PMXT - the unified prediction market API",
5
5
  "type": "module",
6
6
  "bin": {