Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Various questions & feedback

未关闭
#237 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
javascript, json
领域
api

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Bikeshed
星标
4.7k
派生
328
平均合并
2 天 15 小时
30 天内合并 PR
16

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

webmachinelearning/webmcp 的其他 Issue

查看 webmachinelearning/webmcp 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。