@bicharts/chart-mcp 0.6.52 → 0.6.55

package/README.md

@@ -22,7 +22,7 @@ What that buys you: a working, interactive chart that **fits your data on the fi
 try** — real source you commit, with no D3, Vega or charting-API expertise in the
 loop, and a solid starting point to adjust rather than a blank page. Because the
 engine knows what ~90 chart types can honestly say, it will sometimes propose a view
-— or a measure — you had not thought to ask for. Three tools:
+— or a measure — you had not thought to ask for. The main tools:
 
 - **`assess_data_shape`** — profiles a CSV **locally** with the same measurement
   engine the Power BI visual uses (`@bicharts/shape-core`). No backend call, no
@@ -42,6 +42,12 @@ engine knows what ~90 chart types can honestly say, it will sometimes propose a
   is not the same as no cost, because eligibility *is* the engine's own answer. Free within
   a generous hourly allowance; beyond it a call may draw usage credits. A live licence
   additionally unlocks *draft* types.
+- **`suggest_charts`** — "which charts suit this model?" in one call, for a semantic model in a
+  Microsoft Fabric App on Rayfin's data app template: reads the model's tables, measures and
+  relationships through the project's own `fabric-app-data` CLI, finds its natural views (by place,
+  flows between places, over time, by category), queries each at its grain and asks the eligibility
+  engine what fits each, replying with the real counts. Each view saves its rows for
+  `generate_chart`. One `list_eligible_charts`-style metered call per view.
 - **`generate_chart`** — profiles locally, then calls the BIC backend, which picks
   an eligible chart type for the measured shape (or honors `chart_type`) and
   returns code that has passed the backend's gates/QC. Renderer selection is the same