Skip to content

Clarify executeTool input and schema values - #279

Merged
domfarolino merged 2 commits into
webmachinelearning:mainfrom
mlmrx:ml/clarify-executetool-values
Sep 26, 2026
Merged

domfarolino merged 2 commits into
webmachinelearning:mainfrom
mlmrx:ml/clarify-executetool-values

Conversation

@mlmrx

@mlmrx mlmrx commented Sep 1, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • clarify that executeTool() takes a RegisteredTool returned by getTools()
  • clarify that RegisteredTool.inputSchema is exposed as a parsed JavaScript object
  • clarify that callers pass the structured JavaScript input value directly rather than pre-serializing it with JSON.stringify()
  • add a focused discovery-and-execution example to the API introduction

This documents the contract already defined by the RegisteredTool dictionary and the
executeTool() serialization algorithm. An implementation that exposes inputSchema as a string or
requires pre-serialized JSON arguments does not match the current draft.

Closes #278.

Validation

  • W3C spec-generator: Bikeshed processing with die-on=warning
  • git diff --check

Preview | Diff

Comment thread index.bs Resolved
Comment thread index.bs Resolved
Comment thread index.bs Resolved
@domfarolino
domfarolino merged commit 69b73b4 into webmachinelearning:main Sep 26, 2026
2 checks passed
github-actions Bot added a commit that referenced this pull request Sep 26, 2026
…279)

SHA: 69b73b4
Reason: push, by domfarolino

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify executeTool argument encoding and returned schema shape

2 participants