@mulmoclaude/core 2.0.0 → 2.0.1
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.
|
@@ -863,3 +863,35 @@ afterwards; the load happens once at boot.
|
|
|
863
863
|
Do NOT tell the user to re-check the spelling in `.env`, add the key
|
|
864
864
|
again, or move it elsewhere; the file is already correct, and it is being
|
|
865
865
|
read. The conflict is the whole problem.
|
|
866
|
+
|
|
867
|
+
## A tool your own instructions describe returns "No such tool available"
|
|
868
|
+
|
|
869
|
+
### Symptoms
|
|
870
|
+
|
|
871
|
+
- The Plugin Instructions section of your system prompt documents a tool
|
|
872
|
+
(`mcp__mulmoclaude__google`, `mcp__mulmoclaude__manageSpotify`, any
|
|
873
|
+
plugin-backed name), but calling it errors with `No such tool available`.
|
|
874
|
+
- `ToolSearch select:<that name>` reports no matching deferred tool either.
|
|
875
|
+
- Static tools in the same session (`presentDocument`, `presentForm`, …) work.
|
|
876
|
+
|
|
877
|
+
### Cause
|
|
878
|
+
|
|
879
|
+
The tool surface is published by a separate MCP broker process, and plugin-backed
|
|
880
|
+
tools register there a moment after the session's tool list is first taken. A
|
|
881
|
+
session that captured the list too early keeps one that lacks exactly those
|
|
882
|
+
tools — while the system prompt, built in the server where the plugin IS
|
|
883
|
+
registered, still describes them.
|
|
884
|
+
|
|
885
|
+
### Fix
|
|
886
|
+
|
|
887
|
+
Tell the user plainly that the tool is unavailable in THIS session and that
|
|
888
|
+
starting a new chat re-takes the tool list. Do NOT invent a fallback: reading
|
|
889
|
+
the account's stored credentials, shelling out to a provider CLI, or
|
|
890
|
+
reconstructing the call by hand is worse than the missing tool, and it is not
|
|
891
|
+
what the user asked for.
|
|
892
|
+
|
|
893
|
+
If a new chat has the same gap, the broker did not publish the tool at all.
|
|
894
|
+
Ask the user for the server log around the session start — the broker prints
|
|
895
|
+
`[mcp-server] publishing N tools: …` and, when a promised tool is missing,
|
|
896
|
+
`[mcp-server] advertised but NOT published (check plugin load above): …`. That
|
|
897
|
+
second line, with the plugin-load errors above it, is what a bug report needs.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mulmoclaude/core",
|
|
3
|
-
"version": "2.0.
|
|
3
|
+
"version": "2.0.1",
|
|
4
4
|
"description": "Shared server-side core for MulmoClaude and MulmoTerminal — the always-shipped-together subsystems consolidated behind subpath exports so the two hosts can't drift. Server-only except the browser-safe ./artifacts, ./whisper/client, ./workspace-setup/slug, ./translation/client, ./remote-view, ./remote-host and ./plugin-vue entries. All host specifics are injected.",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|