Check a draft says what they mean
notebook_fidelity_checkBefore the user sends something, gather what is needed to check it privately against what they meant and the notebook entries it came from: the draft, the source text, and the things to look for — dropped conditions, a leaning presented as a decision, an inference presented as their position, an unclear ask, a commitment they did not make, background the recipient will not have. This server runs no analysis and returns no verdict; you do the reading and show the user what you found as suggestions. It rewrites nothing and sends nothing, and none of it reaches the recipient. Reads only. This is the user's RelayLink notebook, for material they are keeping: use it when they name RelayLink or their notebook, when they are continuing work already kept here, or when they pick a RelayLink entry. A durable fact ABOUT them — how they like to be worked with, what they are working on — is memory_add's instead, and a project-scoped preference or one with an end date is this notebook's. A bare "add a task" or "save this note" may be meant for another connected app, and a destination they name outright is always the destination. If more than one place is plausible and nothing settles it, ask once, then stay with the answer for the rest of the task.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"intent": "<intent>"
},
"name": "notebook_fidelity_check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| intent | Yes | What the user actually means to get across, in their words. | |
| draftId | No | A draft_id from draft_package or notebook_share, to read the pending draft itself. | |
| entryIds | No | The entry_ids the message is supposed to be faithful to. | |
| draftText | No | The outgoing text, if it is not a saved draft yet. |