Memory
Operator prior art (2026-10-08, from their built system): MCP tool-name semantics matter enormously BUT the connection name is user-chosen and becomes the tool prefix in most clients — outside our control. Solution that worked ("hilariously successful", Claude proactively recommends it): mcp_ui embedded iframe — own app UI for loading documents/entering prompts (handled by our system), plus a model-facing descriptor (what it does, troubleshooting steps, what to expect when user finishes). Design consequences recorded: (1) semantic load must sit in the suffix we control (verb-first stable names) + descriptions written assuming the prefix is noise — descriptions outweigh names since models read them; suggest a default connection name in setup docs but never depend on it; (2) iframe is the primary funnel surface, verdict tools the machine backplane; (3) iframe interactions happen inside our perimeter → loggable/receiptable (compliance superpower vs free chat); enforcement stays server-side regardless. Status: folds into the five-tool-contracts draft on operator nod.
[Digest: 53df278b-50a4-44ed-a3d2-156dfa06cc37]
Tags: mcp-ui, funnel, tool-naming, prior-art, project:redaction-kernel, kind:episodic, rolled-up — Source: mcp — 2026-10-08 13:37:03 UTC