@chessceo/mcp 0.49.7 → 0.49.8
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/docs/engine-usage.md +19 -0
- package/package.json +1 -1
package/docs/engine-usage.md
CHANGED
|
@@ -192,6 +192,25 @@ Override the defaults with `stockfish_multipv` / `lc0_multipv` when a specific p
|
|
|
192
192
|
|
|
193
193
|
The skipped engine's field is omitted from the response (not present as an empty object).
|
|
194
194
|
|
|
195
|
+
## Renting and choosing engines
|
|
196
|
+
|
|
197
|
+
Analysis needs a running rental. Start one with `start_cloud_engine`, using a `machine_type` SKU from `list_cloud_machine_options`. Each SKU provides one of three shapes, shown in its `engine` field:
|
|
198
|
+
|
|
199
|
+
- **`stockfish`**: Stockfish only. Fits when the question is objective (is this tactic real, does this defense hold).
|
|
200
|
+
- **`lc0`**: Lc0 only. Fits the practical, human-feel read, or running alongside a `deep_analyse` that holds the Stockfish side.
|
|
201
|
+
- **`combo`**: both engines in one container. The default, and the right choice for prep decisions, where both reads are needed on the same position.
|
|
202
|
+
|
|
203
|
+
Rule of thumb: start a `combo` rental unless the task only needs one engine. A single-engine rental gives one read per position, so a prep walk that needs both reads on a single-engine rental takes two passes.
|
|
204
|
+
|
|
205
|
+
`list_cloud_machine_options` returns the price for each SKU. Show the user the price and get their confirmation before starting a rental; every rental bills per second until `stop_cloud_engine`.
|
|
206
|
+
|
|
207
|
+
Routing to a rental:
|
|
208
|
+
|
|
209
|
+
- `cloud_analyse`, `auto_evaluate`, and `deep_analyse` each take an optional `contract_id` (from `list_cloud_engines`).
|
|
210
|
+
- Without `contract_id`, the call uses the only running rental that can serve the request. If several can, the error lists their contract ids, and you pick one.
|
|
211
|
+
- Any shape works. With `engines` set, the rental must provide those engines: asking for `engines: ["lc0"]` on a stockfish-only rental fails.
|
|
212
|
+
- Do not guess contract ids. Call `list_cloud_engines` first if more than one rental is running.
|
|
213
|
+
|
|
195
214
|
## Worked example
|
|
196
215
|
|
|
197
216
|
User is preparing Black against a 2600 opponent who plays 1.e4 c5 2.Nf3 d6 3.d4 cxd4 4.Nxd4 Nf6 5.Nc3 a6 6.Be3 e5. You want to know if 7.Nb3 or 7.Nf3 is more testing.
|
package/package.json
CHANGED