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

Abierto
#2,913 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
65/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
api

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Java
Estrellas
10.7k
Forks
1.5k
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/copilot-sdk

Todos los issues de github/copilot-sdk

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.