@bicharts/chart-mcp 0.6.90 → 0.6.92

package/README.md

@@ -79,6 +79,7 @@ only render text); `structuredContent` is for code, so nothing has to string-par
 | --- | --- |
 | `code` | the `render()` source (omitted when `include_code: false`, which is the default when `out_dir` is given - the code is then on disk) |
 | `chartName`, `language`, `version`, `creditCost` | what was produced, and what it cost |
+| `capabilities` | present only when the chart's type takes chart-host's lasso (a drag around marks selects the ones inside, through the selection a click makes): `{ lasso: { rowCap? } }`. The component written with the chart already passes `lasso: { capable: true, enabled: true }` in its options; a host written by hand passes the same, and `lasso: { enabled: false }` turns it off |
 | `correlationId` | the handle into the server-side log — quote it in any support request |
 | `outputHash` | the server's identity for this exact code (the same code always carries the same hash) — keep it with the chart |
 | `requiredD3Plugins` | packages the code calls, e.g. `["d3-sankey"]` — install them and pass the host **one** d3 that carries them, built with `assembleD3(d3, { ...plugins })` from `@bicharts/chart-host` (assigning onto an ES-module `d3` namespace throws), or the chart throws mid-render |
@@ -270,7 +271,7 @@ else:
 There's no usage counter: the service counts calls from the requests it receives.
 `assess_data_shape` never sends anything - it profiles your data locally, telemetry on or off.
 
-Set `BIC_MCP_TELEMETRY=0` in the server's environment to turn all three off.
+Set `BIC_MCP_TELEMETRY=0` (`false`, `off` and `no` work too, in any case) in the server's environment to turn all three off.
 
 Three other things leave your machine, none of them telemetry:
 
@@ -310,6 +311,8 @@ and `GET /healthz`. What's different from the local server:
 - **Each request it sends says it came from the hosted server,** and an `X-BIC-Client-IP` header on the incoming
   request is passed on, so the service's limits apply to the person rather than to the server. Run it yourself only
   behind something that checks callers, since it trusts that header.
+- **The service records the names of the arguments each tool call passes, never their values:** which settings
+  agents use, counted without reading what anyone asked for. The local server sends nothing of the kind.
 
 ## The agent skill (recommended)