Skip to content

Commit f288380

Browse files
committed
webmcp: cite #243 — this is an implementation lag, not an open spec question
The comment said the IDL and Chrome 'disagree'. Accurate, but it reads as though the divergence is unresolved. It is not: webmachinelearning/webmcp#243 settled it on 2026-08-17 (closed completed) and the IDL now says object; Chrome 151 has not shipped that resolution yet. That distinction matters to anyone who reads this file and also reads that tracker. Behaviour is unchanged — string first, object as fallback — which is already correct both today and on the day Chrome converges.
1 parent 0d419eb commit f288380

1 file changed

Lines changed: 7 additions & 5 deletions

File tree

‎src/webmcp.js‎

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -347,13 +347,15 @@ export async function runTool(name, input, { signal } = {}) {
347347
if (!tool) return `${name} is not in order right now, so there is no tool to call.`;
348348
// SETTLED EMPIRICALLY, Chrome 151, 2026-08-29 against this deploy.
349349
//
350-
// The normative IDL types executeTool's second argument as `object`; Chrome's
351-
// imperative-API doc passes a JSON STRING. They disagree, so we measured it:
350+
// The normative IDL types executeTool's second argument as `object`. That was settled
351+
// upstream in webmachinelearning/webmcp#243 ("executeTool() should take an object, not
352+
// a string"), closed as completed 2026-08-17 — so this is not an open spec question,
353+
// it is Chrome not having shipped the resolution yet. Measured on 151.0.7922.171:
352354
// executeTool(tool, { goal: '…' }) -> UnknownError: Failed to parse input arguments
353355
// executeTool(tool, JSON.stringify({ goal:'…' })) -> resolves
354-
// Chrome wants the string. We send the string first and keep the object path as
355-
// the fallback, so mace stays correct against both readings and will not break
356-
// when the implementation converges on the IDL.
356+
// Chrome wants the string today. We send the string first and keep the object path as
357+
// the fallback, so mace is correct on 151 AND already correct on the day Chrome ships
358+
// #243 — no change needed here when it lands.
357359
try {
358360
return await modelContext.executeTool(tool, JSON.stringify(input ?? {}), { signal });
359361
} catch (e) {

0 commit comments

Comments
 (0)