Various questions & feedback
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- javascript, json
- Domain
- api
Research direction
The issue raises questions about the WebMCP spec and links issue #236, but names no spec files or tests. Start by reading the linked issue and the spec sections quoted here; the questions span browsing context, origin isolation, tool progress and execution, schemas, and observations. Done would require the maintainers to resolve the questions and define concrete changes.
Written by the indexing model from the issue text.
Description
Noting this all down in one place ahead of a meeting. I only read through the spec and explainers on a plane, so apologies if this is stuff that's already been discussed. If anything isn't a quick answer, I can create a separate issue.
Also see https://github.com/webmachinelearning/webmcp/issues/236.
Browsing context required: As tool calls are handled in JavaScript, a browser tab or a webview must be opened to provide a visible interface and browser context. In other words, there is no support for agents or assistive tools to call tools in a headless state.
Why? Headless browsers have a browsing context right?
WebMCP is only available in origin-isolated documents. This ensures that the document's origin remains stable throughout the tool's lifetime.
Why? Not saying it's wrong, just don't understand. postMessage doesn't have this limitation.
Can tools provide progress? Seems like a job for a stream/observable!
How does document.modelContext access work across origin for exposed tools? (document access will be blocked right?)
Why is inputSchema stringified? Seems a bit weird.
The browser agent, on the other hand, does not run JavaScript on the page.
I guess you're already on top of this, but the same should happen for executing tools.
Using JSON schema seems a bit… WebSQL. Is the format frozen? What if it's changed in future? I assume there's no actual casting/validation of the format?
Do we need an output schema? So, if the function returns an object, the agent can understand how the various keys can be used.
Should an observation be required before attempting to call a tool? In case things have changed.
- Dominant language
- Bikeshed
- Stars
- 4.7k
- Forks
- 328
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 15
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from webmachinelearning/webmcp
-
Say how an agent should weigh annotations that the page wrote about itselfPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
webmachinelearning/webmcp#353 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
webmachinelearning/webmcp#343 · 1 reaction ·
Maintainers usually reply within 1 day
-
Agenda+ i18n-tracker
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
webmachinelearning/webmcp#273 · 3 comments ·
Maintainers usually reply within 1 day
-
a11y-tracker Agenda+
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
webmachinelearning/webmcp#272 · 4 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
webmachinelearning/webmcp#234 · 5 comments ·
Maintainers usually reply within 1 day
All issues in webmachinelearning/webmcp
Similar issues
-
area:editor bug issue-form:bug P0 platform:windows review: low
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
1lck/Lithe-IDEA#1388 ·
Maintainers usually reply within 1 day
-
fix(api): isToolAuditEnabled swallows database read errors on auditToolOperations without loggingOpenarea: backend bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
snapotter-hq/SnapOtter#3238 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#32805 ·
Maintainers usually reply within 1 day
-
rig up --plan times out after 5 s and reports an UNKNOWN outcome while the daemon completes the planOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day