.NET SDK: MCP server config has no way to set per-server tool deferral (deferTools)

未關閉
#2,913 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
65/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
csharp
領域
api

研究方向

Start by locating the .NET definitions of McpServerConfig, McpHttpServerConfig and McpStdioServerConfig, then check how their settings are serialized and tested. Compare the SDK's existing configuration patterns with the stated protocol values, auto and never. Done means each MCP server config can express deferTools and tests verify the setting is carried through.

由索引模型根據 Issue 內容生成。

描述

Problem

With tool search enabled, a session defers every MCP server's tools behind the tool-search tool. The runtime protocol lets a session control this per server: McpServerConfigDeferTools, with auto (tools may be deferred) and never (tools are always in the initial tool list, even when tool search is enabled). The Python and Rust SDKs expose this setting.

The .NET SDK doesn't. McpServerConfig, McpHttpServerConfig and McpStdioServerConfig have no member for it. Their only members are Type, Tools and Timeout, plus Url, Headers and the OAuth settings for HTTP, and Command, Args, Env and WorkingDirectory for stdio.

Impact

A .NET host can't enable tool search and still keep a chosen MCP server's tools always loaded. It has two options:

  • enable tool search, and every MCP server is deferred, including servers whose tools are needed on almost every turn, which adds a search step before they can be used;
  • leave tool search off, and every tool definition from every server is sent on every model call.

ToolSearchConfig (Enabled, DeferThreshold) applies to the whole session, so it can't single out a server. Per-tool defer exists only for tools the host registers itself, not for MCP server tools.

Environment

  • .NET SDK, with tool search enabled through SessionConfig.ToolSearch and HTTP MCP servers.
主要語言
Java
星號
10.7k
分支
1.5k
PR 合併指標
30 天內沒有已合併 PR

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

github/copilot-sdk 的其他 Issue

查看 github/copilot-sdk 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。