@battlegrid/mcp-server 32.0.28 → 32.0.29

package/dist/index.d.ts

@@ -47,7 +47,7 @@ import { Client, StreamableHTTPClientTransport } from '@modelcontextprotocol/cli
  * being asked. Move it for a change to THIS package — a proxy fix, a dependency bump, a docs
  * correction. Never move it to track the server.
  */
-export declare const PACKAGE_VERSION = "32.0.28";
+export declare const PACKAGE_VERSION = "32.0.29";
 export declare const DEFAULT_URL = "https://mcp.battlegrid.trade/mcp";
 export interface EnvConfig {
     apiKeys: string[];

package/dist/index.js

@@ -49,7 +49,7 @@ import { Client, SdkHttpError, StreamableHTTPClientTransport } from '@modelconte
  * being asked. Move it for a change to THIS package — a proxy fix, a dependency bump, a docs
  * correction. Never move it to track the server.
  */
-export const PACKAGE_VERSION = '32.0.28';
+export const PACKAGE_VERSION = '32.0.29';
 export const DEFAULT_URL = 'https://mcp.battlegrid.trade/mcp';
 const MAX_RETRIES = 3;
 const RETRY_DELAYS_MS = [2000, 4000, 8000];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@battlegrid/mcp-server",
-  "version": "32.0.28",
+  "version": "32.0.29",
   "description": "BattleGrid MCP server — play crypto prediction games from AI agents",
   "type": "module",
   "main": "dist/index.js",

package/skills/EXPORT.json

@@ -1,25 +1,25 @@
 {
   "generator": "battlegrid-app/server/scripts/export-mcp-skills.mjs",
-  "contractVersion": "129.1.0",
+  "contractVersion": "132.0.0",
   "files": {
-    "battlegrid-agent-management/SKILL.md": "18c635d512ba0b9e17df11d157adff5aed0bd8cc0bfa32df3e53b5e9d3453e45",
+    "battlegrid-agent-management/SKILL.md": "91d1be4de1e33d54e1852c970af66ad176068fd16c30b4326e49053b7a35eb32",
     "battlegrid-agent-management/references/agent-stage-examples.md": "dffcc353d61dfc7b5bb6a2b3077fc6bf8c760a34c287cafb3b59b99306f24195",
-    "battlegrid-arena-play/SKILL.md": "ec55a4ed41f4e54a66ddc66ef3e9e9c87c31986e83f1d66c2ae91f3557bad514",
+    "battlegrid-arena-play/SKILL.md": "fdaabcd2e5ce3946ee96e553ce2e1931a822b84f91b0c94ce86a8bde0cc1d50f",
     "battlegrid-arena-play/references/entry-stage-examples.md": "0223f3743171ff213e943789d27590b2f65648398e85e10cd24938d5eb6af665",
     "battlegrid-market-analysis/SKILL.md": "fcbe98e30e1edce39bb170c224cdf20181934f62b5f3a26b293787c70eeb6229",
     "battlegrid-officers/SKILL.md": "3fd59ec301d1492c956fbdb4368fef61f29abd137f02f49a6172351c7a563309",
     "battlegrid-officers/references/officer-stage-examples.md": "ef46ba26f4b36c9964b5bde95fdf98e5952c3786b77be5f136056cac792f0aec",
-    "battlegrid-radar-deployment/SKILL.md": "b344cd3d2051153115ce9840606e6a08a140f704d5da6a10fca18d81c3796be6",
+    "battlegrid-radar-deployment/SKILL.md": "42900772033d799ce8eeeea9a433d76dd54fb5b153c83951753f73859dcfc021",
     "battlegrid-radar-deployment/references/arena-stage-examples.md": "d27cfed1f4663f267c4a7ecebe4a6e65a450fc74bd14ce8987fb61af5bbf2ca5",
     "battlegrid-radar-deployment/references/radar-stage-examples.md": "13fc3f55d91d3da9754e1ed7fb27493b7b7ba4d40a6a7e8d1ee0365f90ea10de",
     "battlegrid-strategy-authoring/SKILL.md": "39cfa46b1f640e6800edb7e85a8f2c4b6b8786cddf71bb8244d172a44fc11d75",
     "battlegrid-strategy-authoring/references/strategy-stage-examples.md": "f10ecdc91f3660a708eee7a7bacefce2acbb46c9cf7e0ac1454bd54f839f39fd",
-    "battlegrid-strategy-doctor/SKILL.md": "f15bce81a95b3cc6f1e8ebf3008ec56f7d100f74a5e3e85fc46cdd26554ed807",
+    "battlegrid-strategy-doctor/SKILL.md": "24c2208cf6832f1fc34e1b1c52acd8dae10f56b9860aaf27b450a62a9fb74634",
     "battlegrid-strategy-examples/SKILL.md": "9d18bf0e4bf85a28508e2881a4cdf77b823ec831e7cec5d82f82dc251402f41c",
     "battlegrid-strategy-examples/references/playbooks.md": "a9464789df2e762faf9dbd7845101564bc1847cd193f709f8ac4b6bff08f09dd",
     "battlegrid-strategy-examples/references/recipes.md": "806aae0b4842408f6e6ed3e108293073f4f31d1c27fa419ad57df9e1134f23e7",
     "battlegrid-strategy-examples/references/tradingview-ports.md": "c62ce72b741abe5a92e1dec6615f26b19a54959aa1d29542518cd9a189390b98",
-    "battlegrid-trade-analysis/SKILL.md": "cc401a0c842be53df3725344db2e5446325c05ab580e8fa50cb9a6189de9e327",
-    "battlegrid-trade-proposal/SKILL.md": "8e20ce1206ae51f1f87c6e940c8b7ed2798dcd2dfc8d9a2f82adf1a4d0817313"
+    "battlegrid-trade-analysis/SKILL.md": "140d847f24e98845736d4f0c2e72b318a4d235413f72f072d2fe6d0daa5f64db",
+    "battlegrid-trade-proposal/SKILL.md": "bf8f3794478cdecc989020bd775c3c91744f72b440b1a90f88f6700c9a61ca24"
   }
 }

package/skills/battlegrid-agent-management/SKILL.md

@@ -95,7 +95,11 @@ places, against the order floor, and whether that is `feasible`. Then one confir
 strategy, the model, and the budget posture** — the capital ceiling and stops the trading
 configuration will carry, or that it will take the platform seed, with the smallest order against
 the floor — and on the player's explicit pick call `commit_agent_draft` with the `agentId`, that
-read's `draftVersion` and `expectedRevision: null`. A reading with `feasible: false` is a create the
+read's `draftVersion`, `expectedRevision: null` and the `teamId` of the team the agent is created on.
+**The team is the commit's, never the draft's**: read `get_account_state`, which lists the player's
+`teams`, name the team in the confirmation — the agent trades on that team's wallet and spends its
+balance — and default to the Main team unless the player names another. A create commit without a
+team is refused. A reading with `feasible: false` is a create the
 commit will refuse: say so, and stage a larger ceiling or a looser configuration first. Where the player has the create screen open, their own Create is the
 other way to commit it.
 
@@ -136,7 +140,9 @@ mid-edit in their form**, and every change you make joins it. Then:
 - **Commit** through step 4: read the draft with `get_agent_draft`, state the radius from its diff
   and impact, confirm, and on the player's explicit pick call `commit_agent_draft` with the
   `agentId` and exactly the `draftVersion` and, as `expectedRevision`, the `committedRevision` that
-  read returned. The commit publishes every axis the draft holds — the player's own unsaved edits
+  read returned, and `teamId: null`: a commit never moves an agent to another team, and an edit
+  commit naming a team is refused. Moving an agent between teams is the player's step in the web
+  app, allowed only once the agent is drained. The commit publishes every axis the draft holds — the player's own unsaved edits
   included — so the confirmation reads out the whole diff, not only your proposal. Where their form
   is open, their own Save is the other way to commit it.
 - **Discard** only on the player's word. `get_agent_draft` is the read of what a discard destroys:
@@ -159,7 +165,7 @@ again only on their word.
 
 Every one of a draft commit (an edit or a rebind), halt, resume, activate and archive runs this
 shape. The reads (`get_agent_budget`, `list_user_active_positions`, `get_agent_automation_status`,
-`get_agent_performance`, `get_agent_thought_log`) need no confirm and
+`get_agent_performance`, `list_agent_market_grid_decisions`) need no confirm and
 cost nothing but a call — do them first, always.
 
 State the blast radius **from server fields, as numbers**, before the confirm form:

package/skills/battlegrid-arena-play/SKILL.md

@@ -29,7 +29,12 @@ fee. The grid you commit is the one that gets scored, and there is no undo.
 ### 1. Account state first
 
 `get_account_state`. It carries the balance, the rank, and **`mcpWagerEnabled`** — a served
-projection of the player's Server-Signed Wagers signer consent.
+projection of the player's Server-Signed Wagers signer consent on **Main**, the team that pays the
+player's own entry. `balance` is Main's too; the total across every team is `allTeamsBalance`.
+
+An **agent's** entry is paid by the agent's own team, never by Main on its behalf. For an agent
+entry, read that team's row in `teams` — `teams[].readiness.canPayArena` is the served verdict —
+instead of `mcpWagerEnabled`.
 
 - **False** ⇒ a **definite refusal**, before any submission. Say so up front, name the enablement
   path (Profile → Wallet tab → enable Agent Wagers), and continue **read-only**: sessions, market
@@ -151,7 +156,8 @@ player's, and the attribution is part of what was scored.
   `reasoning` is null when no record describes the current picks — say that rather than
   reconstructing one, and a pick missing from `reasoning.picks` is one the player chose.
   `list_my_market_grid_entries` is the history across sessions. An agent's decisions are a different
-  record, `get_agent_thought_log`.
+  record, `list_agent_market_grid_decisions`: each arena decision the agent's model reached, with its
+  session — a stand-down before any model call is only in `get_agent_activity_feed`.
 
 ## On the arena's session page
 

package/skills/battlegrid-radar-deployment/SKILL.md

@@ -257,10 +257,18 @@ the reason — and **names what the change does to the stored policy**, read fro
 
 Then:
 
-- **Radar** → `commit_radar_deployment_draft({ coinId, draftVersion, expectedRevision })`,
+- **Radar** → `commit_radar_deployment_draft({ coinId, draftVersion, expectedRevision, teamId })`,
   naming exactly the `draftVersion` and `committedRevision` your draft read returned — the version
   your preview resolved. Ask with `ask_user` first and commit only after an explicit confirming pick.
   The axes it published leave the draft.
+  `teamId` is the team the deployment trades on, and a team is never drafted. For a deployed coin,
+  pass the `teamId` its `list_radar_deployments` (or `get_radar_deployment`) row carries: a
+  deployment keeps its team for life, and another team is a CONFLICT naming the stored one. For a
+  first deployment, choose one of the player's teams from `get_account_state.teams` (ask when there
+  is more than one) and name it in the confirmation. Every slot agent must trade on that team. A
+  platform agent trades on Main, so it fits only a Main deployment. A slot agent of another team is a
+  VALIDATION_ERROR naming the agent and its team. The draft read reports it beforehand for a deployed
+  coin, and for a first deployment it reports slot agents that trade on different teams.
 - **Arena** → `commit_deployment_policy_draft({ presetId, draftVersion, expectedRevision })`,
   the same way.
 
@@ -420,7 +428,7 @@ whose outcome you did not see.
 ## `test_generate_deployment_grid`
 
 This one runs a **billed LLM generation** against the player's intelligence credits and writes
-thought and activity records. It is a composition aid for tuning an Arena deployment — say that it
+decision and activity records. It is a composition aid for tuning an Arena deployment — say that it
 is billed **before** invoking it, and only invoke it when the player is actually iterating on slots
 and wants to see what the resolved agent would produce. It is never a diagnostic read.
 

package/skills/battlegrid-strategy-doctor/SKILL.md

@@ -57,9 +57,11 @@ Three reads, and they are not interchangeable:
   — they describe different stages and merging them invents a cause.
 - Render every code through its display meta. A raw `NO_ENTRY_CONDITION` or `OPEN_POSITION_CONFLICT` on
   screen is a system identifier leaking into an explanation.
-- **`get_agent_decision_context` reads the decision behind an OPEN position.** It is keyed by coin
-  and answers only for the agent position open on it; for a coin with nothing open it is `null`, so
-  it never explains a trade that did not happen. For "why did nothing happen on SOL", read
+- **`get_agent_decision_context` reads the decision behind an OPEN position.** It is keyed by team
+  and coin and answers only for the agent position open there; for a coin with nothing open on that
+  team it is `null`, so it never explains a trade that did not happen. Without a `teamId` it reads
+  Main, so pass the position's team: the `teamId` of its `list_user_active_positions` row, or the
+  agent's `tradingTeamId` on `get_agents_hub`, or a `list_radar_deployments` row's `teamId`. For "why did nothing happen on SOL", read
   `list_gate_blocks` for the pre-model refusals on that coin, and for a Radar coin
   `get_radar_activity_summary` for its causes, then `get_radar_close_decisions` for the bars it
   decided.
@@ -89,7 +91,8 @@ Three reads, and they are not interchangeable:
 - `list_signal_logs` narrowed by `agentId` when the question is whether the signals fired, as
   distinct from whether the trades made money: its `summary` counts the evaluations and entries, and a
   failed row's `rejection` names why its order was refused. `list_agent_trades` narrowed by `agentId`,
-  `get_agent_thought_log` and `get_agent_activity_feed` for what did happen.
+  `list_agent_market_grid_decisions` and `get_agent_activity_feed` for what did happen, and
+  `get_signal_log`'s `thesisReasoning` for why a trade was taken.
 - **`get_agent_conviction_calibration` honours `readiness`.** An `INSUFFICIENT_DATA` calibration
   carries no win rate — report that there is not yet enough history, never a rate derived from a
   handful of trades.
@@ -162,7 +165,7 @@ it is undetermined.
 ## Negatives
 
 - **Never call `test_generate_deployment_grid`.** It runs a billed LLM generation against the
-  player's intelligence credits and writes thought and activity records. It is the deployment
+  player's intelligence credits and writes decision and activity records. It is the deployment
   flow's composition aid for tuning a draft — it is not a diagnostic read, and running it as one
   charges the player to answer a question the journals already answer.
 - **Never name a strategy write tool, even to forbid it.** Reading a rule is not authority to change

package/skills/battlegrid-trade-analysis/SKILL.md

@@ -34,14 +34,22 @@ Not "what were its returns" — whether it did *the thing it was told to do*.
   by rules it is not running.
 - `get_agent_performance` and `list_agent_trades` narrowed by `agentId` — judge against that mandate. Its
   `summary` and `resultSummary` cover the agent's whole scope on the player's account, not the page.
+- `get_agent_profile` when the question names a period or a signal source — "how did Falcon do this
+  week", "how are its radar trades doing". Pass `timeframe` (`1D`, `7D`, `30D` or `LIFETIME`) and
+  `signalSource`, and quote its KPIs as served — win rate, net P&L, best and worst trade, entry
+  rate, average conviction and risk/reward, durations — recomputing none. `get_agent_performance`
+  measures from the budget baseline, not over a period. A `{ profile: null }` result is
+  **UNDETERMINED** for that agent: the read serves the player's own private agents only. The fixed
+  Decision Quality window and its regime, hour, weekday and coin slices are
+  `get_agent_review_analytics`'s, not this read's.
 - `get_trade_outcome_by_decision` (a trade row's `decisionId`) / `get_trade_chart` when a specific trade
   needs explaining: the outcome carries the fills, fees, slippage, leverage, duration and exit label. A
   measurable trade's `tradeExcursion` reads in R: `mfeR` and `maeR` (the best and worst it reached),
   `exitR`, and `giveBackR` (what it surrendered between its peak and the close). `exitEfficiency` is
   a union — branch on its `state` before reading `efficiencyPercent`. All of them are gross of
   costs; `netPnl` is the after-fee figure.
-- The record around the trades: `get_agent_thought_log` (an agent's decisions), `get_signal_log` (a
-  trade's reasoning and its pipeline), `list_my_market_grid_entries` / `get_my_market_grid_entry` (an
+- The record around the trades: `list_agent_market_grid_decisions` (an agent's arena decisions),
+  `get_signal_log` (a trade's pipeline, its thesis as `thesisReasoning`), `list_my_market_grid_entries` / `get_my_market_grid_entry` (an
   arena entry's reasoning — `agentId` for one agent's entries, none for every entry),
   `get_agent_activity_feed` (what happened), and `get_agent_explorer` for where the agent stands
   among public agents.
@@ -93,13 +101,21 @@ reading a clean report about a messy account learns nothing.
 
 - `list_user_active_positions` for everything at once: it carries the live mark and P&L
   (`markPrice`, `unrealizedPnlUsd`, `roePct`) — check `pricingStatus` and `generatedAtMs` before
-  calling a mark current. Every position is served once, in `positions`, naming its `agentId` and
-  `marketGridSessionId`; `agents` carries each agent's group figures.
+  calling a mark current. Every position is served once, in `positions`, naming its `agentId`,
+  `marketGridSessionId` and `teamId` — the team whose wallet it trades on; `agents` carries each
+  agent's group figures.
 - For each open position, report its protections **and how far the live mark sits from each
   trigger** — a stop is a number the player cannot act on; "3.1% from the stop" is one they can.
 - `list_agent_open_orders` is the platform's record of each agent order, naming its `decisionId` and
-  the venue's `exchangeOrderId` and `cloid`. `get_open_orders` reads the exchange directly — slower,
-  and it fails when the exchange is unreachable; report that as UNDETERMINED, never as no orders.
+  the venue's `exchangeOrderId` and `cloid`. `get_open_orders` reads one team's wallet on the
+  exchange directly — Main unless you pass a `teamId`, taken from a `list_user_active_positions`,
+  `get_agents_hub` (`tradingTeamId`) or `list_radar_deployments` row; read each team you report on.
+  It is slower, and it fails when the exchange is unreachable; report that as UNDETERMINED, never as
+  no orders.
+- `list_user_fills` is what the venue filled on one team's wallet, newest first — Main unless you
+  pass a `teamId` — every agent's and every manual order's alike, attributed to no agent or decision.
+  One trade's fills are `get_trade_outcome_by_decision`'s, on the trade's `decisionId` from
+  `list_agent_trades`; never assign an account fill to an agent by its coin and time.
 - `get_deployment_policy` / `get_radar_deployment` when the protection state comes from standing
   policy rather than the position itself. `list_gate_blocks` when something looks like it should
   have fired and did not.

package/skills/battlegrid-trade-proposal/SKILL.md

@@ -82,6 +82,11 @@ close executes.
   the whole transcript in stored order — the queued card, the agent's reasoning, its thesis and
   setups, the entry card naming the decision and the position it placed, a no-trade with its reason
   and next coins, or a close answer.
+- When the player asks about an earlier request and its `conversationId` is not in this
+  conversation, find it with `list_trade_conversations`: narrow by the agent's `agentId`, and by
+  `window` (or `since` / `until`) when the player names a period. Open the matching row with
+  `get_trade_conversation`, passing the row's `id` as `conversationId`. Never queue a new request to
+  learn what an earlier one decided.
 - `get_entry_request` re-reads a request until it is answered — including while its close has fired
   and the decision is being composed, and past its deadline until its overdue answer lands.
   `cancel_entry_request` withdraws it only while it still awaits its close; once the close has fired