[Client] `callTool()` cannot defer `input_required` or send a later retry (MRTR)

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

维护者通常 1 天内回复

@xixi-box 已经在做这个了。

开始于 2026年11月22日。

  • #769 来自 @xixi-box —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
php
领域
api

调研方向

Read src/Client/Protocol.php around lines 560-627 and MAX_ROUND_TRIPS at line 69 to see how rounds are resolved through the elicitation handlers, then InputRequestResolver.php:145,163 for the message-only exception thrown from the callback. Check the callTool() signature and the linked pull request #769 before starting, since work may already be under way. Done means an opt-out that returns the raw InputRequiredResult plus a retry path accepting inputResponses and requestState, covered by a test against a tool that returns InputRequiredResult.

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

描述

Package: mcp/sdk 0.9.0; still present in v0.10.0 and main (7155eae)

Repro: $client->callTool('x', [...]) against a tool that returns InputRequiredResult, from a client that wants
to park the request until a human answers hours later.

Actual: Client\Protocol::request() always resolves rounds through the elicitation handlers
(src/Client/Protocol.php:560-627, MAX_ROUND_TRIPS at line 69). requestState is never exposed, and callTool()
takes no inputResponses / requestState. Throwing from the callback gives a message-only RuntimeException
(InputRequestResolver.php:145,163).

Expected: an option to return the raw InputRequiredResult, and a way to send the retry with inputResponses
and requestState. Deferral is what multi-round-trip requests are designed for. I understand automatic resolution
is deliberate (#456); this asks for an opt-out next to it. The Tasks extension (#428) covers task-augmented
requests, not plain MRTR.

Found while building Leash for the Symfony AI & PHP MCP SDK hackathon.

主要语言
PHP
星标
1.7k
派生
206
平均合并
1 天 19 小时
30 天内合并 PR
100

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

modelcontextprotocol/php-sdk 的其他 Issue

查看 modelcontextprotocol/php-sdk 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

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