idiolect-mcp 0.5.2 → 0.6.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.
- package/README.md +17 -25
- package/package.json +1 -1
- package/progressive-catalog.json +311 -5964
- package/public-contract.js +12 -1
- package/server.mjs +11 -276
package/README.md
CHANGED
|
@@ -50,29 +50,26 @@ clients receive one `next` action and never coordinate workflow versions or lock
|
|
|
50
50
|
- **`write`** — drafts writing from requests, facts, notes, or outlines.
|
|
51
51
|
- **`rewrite`** — corrects, summarizes, expands, simplifies, paraphrases, or repurposes existing text.
|
|
52
52
|
- **`refine_writing`** — changes returned writing, applies a template, or records its outcome.
|
|
53
|
-
- **`view_writing_profile`** — lists Writing Profiles and
|
|
54
|
-
- **`
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
- **`add_writing_rule`** — stores a lasting rule in the user's words.
|
|
61
|
-
- **`remove_writing_rule`** — stops following one stored rule.
|
|
62
|
-
- **`remove_writing_sample`** — revokes one ready or waiting sample.
|
|
63
|
-
- **`delete_writing_profile`** — deletes a selected profile.
|
|
53
|
+
- **`view_writing_profile`** — read-only: lists Writing Profiles, shows one, and with `samples` lists its writing.
|
|
54
|
+
- **`manage_profile`** — every change, by `action`: `create_profile`, `add_samples`, `remove_sample`,
|
|
55
|
+
`add_rule`, `remove_rule`, `rename_profile`, `set_current_profile`, `set_default_template`.
|
|
56
|
+
|
|
57
|
+
Deleting a whole profile is done on the website. The former per-action profile tools
|
|
58
|
+
(`add_writing_rule`, `delete_writing_profile` and the rest) still work and answer as
|
|
59
|
+
`manage_profile` with that action, but are not advertised.
|
|
64
60
|
|
|
65
61
|
Profile creation, approved samples, and lasting preferences can be part of writing and
|
|
66
62
|
revision workflows. They do not require a separate profile-management request. Inferred
|
|
67
63
|
patterns can contribute approved authored examples; they must not become user-stated rules.
|
|
68
|
-
See [the MCP
|
|
64
|
+
See [the MCP playbook](../docs/MCP-PLAYBOOK.md) for writing and review rules.
|
|
69
65
|
|
|
70
|
-
Cached account-mode tool names
|
|
66
|
+
Cached account-mode tool names that hosts still call forward to the current tool and are not
|
|
67
|
+
advertised; a retired name answers with the current tool to use instead. Slug mode keeps its
|
|
71
68
|
legacy local-samples catalogue; locally configured samples are used only for stateless scoring
|
|
72
69
|
and are not stored.
|
|
73
70
|
|
|
74
71
|
When an account has no Writing Profile, `write` and `rewrite` return the setup choices.
|
|
75
|
-
`
|
|
72
|
+
`manage_profile` with `create_profile` returns exact missing blocks and characters when evidence is thin.
|
|
76
73
|
Feedback can be accepted, corrected-and-accepted, or rejected only against a
|
|
77
74
|
succeeded server-issued output.
|
|
78
75
|
Correction prose is retained only when the applicable consent gates permit it and
|
|
@@ -86,19 +83,14 @@ approved. Creating a profile and
|
|
|
86
83
|
succeeding at a first generation are not activation. Canonical native activation
|
|
87
84
|
occurs only after accepted or corrected-and-accepted feedback.
|
|
88
85
|
|
|
89
|
-
##
|
|
86
|
+
## Words and retries
|
|
90
87
|
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
states cover available, low, zero, unlimited, and temporarily unavailable balances without
|
|
94
|
-
changing the tool names.
|
|
88
|
+
Each account has a monthly word allowance from its plan, plus any extra words it has bought.
|
|
89
|
+
Usage and the plan are shown at idiolect.app/settings/plan.
|
|
95
90
|
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
generation or charging, so their retry object is explicitly scoped to
|
|
100
|
-
`pre_generation`. Successful generation does not yet promise replay after a lost
|
|
101
|
-
response, and paid enforcement remains disabled.
|
|
91
|
+
When an account has no words left, the drafting and rewriting tools return a tool error
|
|
92
|
+
before any generation starts. The error text says how many words were used, when the
|
|
93
|
+
allowance resets, and where to see the plan. Nothing is charged for a refused call.
|
|
102
94
|
|
|
103
95
|
Internal generation coordination happens before provider work. A stale internal
|
|
104
96
|
state is refreshed before the client receives one public retry action. If durable
|