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

Tool `title` and `inputSchema`: what to expose when not provided?

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Read the linked discussion on pull request #223 and compare how WebMCP exposes RegisteredTool#title and inputSchema with MCP behavior. The issue does not settle which API behavior to choose, so first look for a decision in the discussion; done means the exposed values follow the agreed behavior.

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

描述

See https://github.com/webmachinelearning/webmcp/pull/223#discussion_r3620023509 for discussion.

The spec and Chromium implementation always expose the RegisteredTool#title member to JavaScript as a string (empty when not provided), never undefined (see https://crrev.com/c/7742044). We liked this because then the shape of the API is "simple" and the developer doesn't have to reason about what undefined vs "" means. The downside is that we break from MCP, where an MCP client will observe tool.title is undefined if the server doesn't provide it.

Perhaps we should treat title like inputSchema, and expose both as undefined when not provided. Although it's worth noting that this is a different kind of break from MCP, where inputSchema is required there but not in WebMCP.

/cc @beaufortfrancois @liady

主要语言
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 摘要。