holon-ui 0.0.1-dev.2 → 0.0.1-dev.3

package/README.md

@@ -62,17 +62,16 @@ const order = await apps.orders.tools.lookup({ id: "A-1" }, { timeout: 5000 });
 
 An endpoint binding takes `endpoint`, and optionally `authProvider`, `fetch`, and `scoped: true` to close the session after every call. Otherwise a client keeps one session open; call `close()` when the page no longer needs it.
 
-A tool can stop and ask for input through an MCP elicitation. Bind `elicit` to answer it, and the call returns its usual typed output:
+A tool can stop and ask for input through an MCP elicitation. Pass `elicit` to answer it, and the call returns its usual typed output:
 
 ```typescript
-const apps = createApps({
-  orders: {
-    endpoint: "https://orders.example.com/mcp",
-    elicit: async ({ params }) => ({ action: "accept", content: await showForm(params) }),
-  },
+const { shipped } = await apps.orders.tools.ship({ id: "A-1" }, {
+  elicit: async params => ({ action: "accept", content: await showForm(params) }),
 });
 ```
 
+Without `elicit`, the call throws `ToolCallError` with the question on `.result`.
+
 ## Read and watch resources
 
 A server types a JSON resource by registering it with `mimeType: "application/json"` and an `"sh.holon/outputSchema"` JSON Schema in its `_meta`:
@@ -88,7 +87,7 @@ await apps.orders.resources["orders://summary"].watch(value => render(value.open
 
 ## Give tools to the page's agent
 
-`exposeTools` registers the tools of an endpoint-bound client with the page's WebMCP context (`navigator.modelContext`), except those whose `_meta.ui.visibility` omits `"model"`. Calls from the agent go through the client, so they are validated. An agent can only supply arguments, so a question the binding's `elicit` does not answer reaches it as a failed result naming the question. It returns `false` when the browser has no WebMCP context.
+`exposeTools` registers the tools of an endpoint-bound client with the page's WebMCP context (`navigator.modelContext`), except those whose `_meta.ui.visibility` omits `"model"`. Calls from the agent go through the client, so they are validated. An agent can only supply arguments, so a question reaches it as a failed call naming the question; to answer for it, pass an `execute` that calls `callTool` with `elicit`. It returns `false` when the browser has no WebMCP context.
 
 ```typescript
 await exposeTools(apps.orders, { signal: lifetime.signal });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "holon-ui",
-  "version": "0.0.1-dev.2",
+  "version": "0.0.1-dev.3",
   "description": "Typed MCP clients for browser views: MCP Apps host bindings and WebMCP tool exposure.",
   "repository": {
     "type": "git",
@@ -39,7 +39,7 @@
     "fixtures": "node scripts/fixtures.mjs"
   },
   "dependencies": {
-    "holon-sh": "^0.0.1-dev.5"
+    "holon-sh": "^0.0.1-dev.6"
   },
   "peerDependencies": {
     "@modelcontextprotocol/ext-apps": ">=1.0.0"

package/runtime.mjs

@@ -33,10 +33,9 @@ export async function exposeTools(app, options = {}) {
   const { signal } = options;
   const execute = options.execute ?? (async (name, args) => {
     const result = await app.callTool({ name, arguments: args }, { signal });
-    if (result.resultType !== "input_required") return result;
-    // An agent can only supply arguments, so a question it receives would end the call anyway. Bind elicit to answer it.
-    const questions = Object.values(result.inputRequests ?? {}).flatMap(request => request.params?.message ?? []);
-    return { isError: true, content: [{ type: "text", text: [`${name} needs input this page cannot provide`, ...questions].join(": ") }] };
+    // An agent can only supply arguments, so it cannot answer. A custom execute can.
+    if (result.resultType === "input_required") throw new ToolCallError("page", name, result);
+    return result;
   });
   const { tools } = await app.listTools({ signal });
   for (const tool of tools) {