@battlegrid/mcp-server 32.0.74 → 32.0.77

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.
package/README.md CHANGED
@@ -58,6 +58,58 @@ hash moves.
58
58
  64 `equalBars` serves up to 935 (was 467), and 799 at a cap of 200; above 200 an equal column is still refused.
59
59
  `swingLength` keeps its ceiling of 100.
60
60
 
61
+ ## Contract history — v147 to v147.2 (an arena deployment's member is chosen at the bell, agents leave Radar, an entry's fate is journaled)
62
+
63
+ **v147 is MAJOR: published results narrow for inputs v146.14 accepted, and one tool refuses a call it answered.**
64
+ v147.1 and v147.2 are MINOR. Nothing either refuses was accepted by the version before it.
65
+
66
+ ### Reshaped output — one reason v147 is MAJOR
67
+
68
+ - **A deployment resolution names its on-duty members, not one agent.** The RESOLVED arm drops `agentId`,
69
+ `agentDisplayName`, `agentAvatarUrl`, `matchedSlotPriority`, `matchedIsDefault`, `minConfidencePercent` and
70
+ `resolved` for `members`, a non-empty array of those fields: every matching rule on duty in priority order, the
71
+ default only when none matches. Which member plays is decided at the Opening Bell. This moves in
72
+ `preview_deployment_resolution`, `test_generate_deployment_grid`, `get_deployment_policy`,
73
+ `list_deployment_policies` and `get_deployment_policy_draft`.
74
+ - **A test generation reports the members it tried.** `test_generate_deployment_grid`'s RESOLVED result gains
75
+ `tried` (`agentId`, `agentDisplayName`, `admittedCount`, `gridSize`, `stoodAside` per member), and its
76
+ `generation` is null when every on-duty member stood aside.
77
+
78
+ ### New refusals — the other reason v147 is MAJOR
79
+
80
+ - **`generate_agent_grid` refuses an agent whose strategy admits too few coins.** When the strategy admits fewer
81
+ pool coins than the grid needs, the call is a `BAD_REQUEST` with details `{admittedCount, gridSize}`, and a
82
+ pending grid cached for that agent and session is discarded.
83
+ - **A draft slot naming an agent the caller cannot access is refused** by `preview_deployment_resolution` and
84
+ `test_generate_deployment_grid`, in any slot, not only the winning one.
85
+
86
+ ### Added tools — v147.1
87
+
88
+ - **`get_agent_radar_holdings`** (`mcp:read`) serves every Radar deployment of the caller that holds one agent,
89
+ enabled or paused, each with its server-decided withdraw `effect`.
90
+ - **`withdraw_agent_from_radar`** (`mcp:wager`) takes the agent off the holdings it names, each at the policy and
91
+ revision that read returned, and answers one outcome per holding.
92
+
93
+ ### Widened refusal — v147.1
94
+
95
+ - **A `CONFLICT`'s `details.reason` gains `RADAR_WITHDRAW_REFUSED`**, carried with `details.refusals`: one entry
96
+ per refused holding, with its own code and message.
97
+
98
+ ### Widened enum — `get_agent_activity_feed`'s `eventType`
99
+
100
+ - **v147 adds `GRID_STOOD_ASIDE`**: the agent's strategy admitted fewer coins than a grid needs, so it stood aside
101
+ before any spend. A `GRID_SKIPPED` row's `reason` is now a code from one closed vocabulary, not refusal text.
102
+ - **v147.2 adds `GRID_ENTRY_RESOLVED`**: settlement's later word on an agent's entry, with `metadata.resolution`
103
+ `ENTERED` (the fee confirmed after the submit returned), `RELEASED` (the entry could no longer be entered) or
104
+ `REFUND_REQUESTED` (a released entry's landed fee is being returned). A `GRID_SUBMITTED` row's `metadata` also
105
+ carries `entryStatus`: `ENTERED`, or `PAYMENT_PENDING` while the fee is still confirming.
106
+
107
+ ### Re-worded text — v147
108
+
109
+ - The `preview_deployment_resolution` and `test_generate_deployment_grid` descriptions state the on-duty set and
110
+ the member trial. `stage_strategy_draft`'s CONDITIONS axis and the strategies workflow card state that a
111
+ strategy without an entry condition never enters the arena.
112
+
61
113
  ## Contract history — v146.13 (market structure follows LuxAlgo's leg, EQH / EQL read `true`)
62
114
 
63
115
  **Nothing refused at v146.13 that v146.12 accepted at the shipped lookback cap.** One MINOR moves served values
package/dist/index.d.ts CHANGED
@@ -47,7 +47,7 @@ import { Client, StreamableHTTPClientTransport } from '@modelcontextprotocol/cli
47
47
  * being asked. Move it for a change to THIS package — a proxy fix, a dependency bump, a docs
48
48
  * correction. Never move it to track the server.
49
49
  */
50
- export declare const PACKAGE_VERSION = "32.0.74";
50
+ export declare const PACKAGE_VERSION = "32.0.77";
51
51
  export declare const DEFAULT_URL = "https://mcp.battlegrid.trade/mcp";
52
52
  export interface EnvConfig {
53
53
  apiKeys: string[];
package/dist/index.js CHANGED
@@ -49,7 +49,7 @@ import { Client, SdkHttpError, StreamableHTTPClientTransport } from '@modelconte
49
49
  * being asked. Move it for a change to THIS package — a proxy fix, a dependency bump, a docs
50
50
  * correction. Never move it to track the server.
51
51
  */
52
- export const PACKAGE_VERSION = '32.0.74';
52
+ export const PACKAGE_VERSION = '32.0.77';
53
53
  export const DEFAULT_URL = 'https://mcp.battlegrid.trade/mcp';
54
54
  const MAX_RETRIES = 3;
55
55
  const RETRY_DELAYS_MS = [2000, 4000, 8000];
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@battlegrid/mcp-server",
3
- "version": "32.0.74",
3
+ "version": "32.0.77",
4
4
  "description": "BattleGrid MCP server — play crypto prediction games from AI agents",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "generator": "battlegrid-app/server/scripts/export-mcp-skills.mjs",
3
- "contractVersion": "146.14.0",
3
+ "contractVersion": "147.0.0",
4
4
  "files": {
5
5
  "battlegrid-agent-management/SKILL.md": "324ef8181bfcfc99b955d9644ed543c6ab91071153d43f77ccf0a4979b896b09",
6
6
  "battlegrid-agent-management/references/agent-stage-examples.md": "dffcc353d61dfc7b5bb6a2b3077fc6bf8c760a34c287cafb3b59b99306f24195",
@@ -13,10 +13,10 @@
13
13
  "battlegrid-radar-deployment/SKILL.md": "ef291ec096461ed2b78915adbfa41000b959b5803ae4ebef3084bff4c1e1a746",
14
14
  "battlegrid-radar-deployment/references/arena-stage-examples.md": "65af54b67c3248c53fb8911df769ad32824e1f1f1d83ffc007b42a888d5e3076",
15
15
  "battlegrid-radar-deployment/references/radar-stage-examples.md": "7a4195011aa764b106567606f7a2a8ae8e9b2bf74c36b3c74a72379969d70af8",
16
- "battlegrid-strategy-authoring/SKILL.md": "11869b767def2c3951d0f046e8dadeb5a549568399d88bb2df3844e65e3eaf73",
16
+ "battlegrid-strategy-authoring/SKILL.md": "43b6b41e605096ca5db06417961436fd62d7e96cb80a931581910c4a23c1878d",
17
17
  "battlegrid-strategy-authoring/references/strategy-stage-examples.md": "f10ecdc91f3660a708eee7a7bacefce2acbb46c9cf7e0ac1454bd54f839f39fd",
18
18
  "battlegrid-strategy-doctor/SKILL.md": "4be392e51f3b5e76ff4aa22f61700236e8b1e19dfe286aeda8ed98e48a8457ba",
19
- "battlegrid-strategy-examples/SKILL.md": "ac54a2171b3a7bcc0d3e6fa5c75bcf1ee04d5bb2cbfc0d050032d44db5a734d3",
19
+ "battlegrid-strategy-examples/SKILL.md": "a43623e2e5e2ade62d4e2dc1dfd5ce51efda7f15a4024713bc8058ff91beba07",
20
20
  "battlegrid-strategy-examples/references/playbooks.md": "59996c37eea08e7ce398e49304171939e55c968400a1603597d6737faf9e1771",
21
21
  "battlegrid-strategy-examples/references/recipes.md": "ee1b35f5341d3878ef8e8b045d0425a06fb25c76149fe841f2afe075909135f4",
22
22
  "battlegrid-strategy-examples/references/tradingview-ports.md": "ed977b6c190a74777a735cd482e65e65b92b9e8768157b65ea916cabafdf3cd9",
@@ -126,10 +126,12 @@ verdict — gates nothing unless it is itself marked `required`, and an exit rul
126
126
  Whether a sub-rule should be a building block or inlined is answered by the `strategy-examples`
127
127
  skill's **Building block or inline** paragraph. A strategy whose entry conditions include no
128
128
  required and no verdict-carrying condition never routes a trade: every coin fails first with
129
- `NO_ENTRY_CONDITION`, and its draft carries the warning of the same name. It stays a valid
130
- strategy — Market Grid reads it as context — so a strategy the player means to trade needs at least
131
- one. Before any condition is read, a coin must clear the ATR floor, `minAtrPct`, the
132
- TRADE_LEVEL_POLICY dial beside the stop-loss band.
129
+ `NO_ENTRY_CONDITION`, and its draft carries the warning of the same name. It never enters the arena
130
+ either: an arena grid may hold only the coins and directions the entry conditions admit, so an
131
+ agent bound to it sits out every session. It stays a valid strategy, so a strategy the player means
132
+ to trade or play needs at least one. Before any condition is read for a trade, a coin must clear the
133
+ ATR floor, `minAtrPct`, the TRADE_LEVEL_POLICY dial beside the stop-loss band; an arena pick is
134
+ admitted by the entry conditions alone and reads none of the trade dials.
133
135
 
134
136
  **Read the answer, not just the call.** Each of these returns one field that decides a composition
135
137
  question you would otherwise guess — and a refusal you would otherwise earn:
@@ -197,8 +197,10 @@ declares no verdict-carrying condition resolves `null` and constrains no side.
197
197
  `required: true` or carries a verdict (`UP`, `DOWN` or `NEITHER`); a building block not marked
198
198
  `required` gates nothing, and an exit rule never counts. A strategy whose conditions include neither
199
199
  never trades: every coin fails first with `NO_ENTRY_CONDITION`, before the trade levels, the ATR
200
- floor or any condition is read, and its draft carries the `NO_ENTRY_CONDITION` warning. It stays a valid strategy — Market Grid
201
- reads it as context — so this is a choice to state, never an accident. When the agent decides a
200
+ floor or any condition is read, and its draft carries the `NO_ENTRY_CONDITION` warning. It never
201
+ enters the arena either: an arena grid may hold only the coins its required conditions pass, in the
202
+ directions its verdict admits, so an agent bound to a strategy with no entry condition sits out every
203
+ session. It stays a valid strategy, so this is a choice to state, never an accident. When the agent decides a
202
204
  routed trade, its `decide_trade` call cites 1–8 of the evaluated entry conditions in
203
205
  `conditionChecklist`, and only a condition that read TRUE may be cited as `CONFIRM`.
204
206