[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 摘要。