Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[bot] Anthropic MCP connector tool calls (mcp_tool_use/mcp_tool_result) produce broken, input-less child spans

Abierto Apto para principiantes
  • ¿Algo no está bien?
#191 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
82/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java
Área
observability

Línea de trabajo

Comienza en InstrumentationSemConv.addAnthropicServerSideChildSpans en braintrust-sdk/src/main/java/dev/braintrust/instrumentation/InstrumentationSemConv.java, donde los bloques se despachan por type; lee también ANTHROPIC_SERVER_TOOL_USE_TYPE, isAnthropicToolResultType y los fallbacks de call == null. Registra mcp_tool_use como tipo de llamada para que la coincidencia de resultados basada en sufijos existente lo empareje con mcp_tool_result. Refleja la cobertura existente de server_tool_use en BraintrustAnthropicServerSideSpansTest.java y ejecuta esa clase de prueba; hecho significa que el span hijo de MCP lleva el nombre real de la herramienta y input_json.

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

Descripción

bug java

Summary

InstrumentationSemConv.addAnthropicServerSideChildSpans dispatches Anthropic Messages response content blocks by checking each block's "type" against the literal string "server_tool_use" (see ANTHROPIC_SERVER_TOOL_USE_TYPE and the dispatch check). Anthropic's MCP connector feature emits a different, distinct pair of block types for server-executed MCP tool calls: "mcp_tool_use" (the call) and "mcp_tool_result" (the result). "mcp_tool_use" does not match the "server_tool_use" check, so it is never registered in the call-tracking map used to pair calls with results.

Meanwhile "mcp_tool_result" does match the result-type check, which is a suffix check (type.endsWith("_tool_result") && !type.equals("tool_result")). So the result proceeds through the pairing logic, never finds its matching call, and is emitted alone with call == null.

Consequence for every MCP connector tool invocation:

  • The child span is named generically "mcp_tool" (derived by stripping "_tool_result" off the result's type) instead of the real tool name, because the fallback naming path only runs when call == null.
  • input_json is never set on the span, because the input-extraction path also returns null when call == null. The tool's name, server_name, and input arguments — which live only in the dropped mcp_tool_use block — are permanently lost from the structured child span.

The raw response body is still present in the parent LLM span's full JSON passthrough, so the data isn't gone from Braintrust entirely, but the per-tool-call child span that Braintrust's UI specifically surfaces for tool calls is broken for every MCP connector invocation — call name and input are unrecoverable from that span.

Braintrust docs status: supported

Braintrust's docs at https://www.braintrust.dev/docs/integrations/ai-providers/anthropic describe this capability for the Python SDK: tool calls (including MCP connector tool calls) are captured "with its input and result ... named after the tool" as dedicated spans. This confirms the capability is documented/expected, just not delivered correctly by the Java SDK.

Why this isn't speculative

The identical bug (same mechanism: literal match on "server_tool_use", suffix-based result matching that doesn't require a paired call) was already found and fixed in Braintrust's Python SDK — see braintrustdata/braintrust-sdk-python#797 (fixed in py-sdk-v0.44.1) — and is tracked as still-open for the Go SDK in braintrustdata/braintrust-sdk-go#107. The fix was never ported to the Java SDK.

Upstream sources

Local repo files inspected

  • braintrust-sdk/src/main/java/dev/braintrust/instrumentation/InstrumentationSemConv.java — ANTHROPIC_SERVER_TOOL_USE_TYPE constant and dispatch check; addAnthropicServerSideChildSpans (call registration loop); isAnthropicToolResultType (suffix-based result matching); emitAnthropicServerToolSpan, anthropicToolSpanName, anthropicToolSpanInput (fallback behavior when call == null).
  • braintrust-sdk/instrumentation/anthropic_2_2_0/src/test/java/dev/braintrust/instrumentation/anthropic/v2_2_0/BraintrustAnthropicServerSideSpansTest.java — only exercises web_search/server_tool_use; no mcp_tool_use/mcp_tool_result test coverage exists.
  • Repo-wide search for mcp_tool_use / mcp_tool_result / "MCP connector" — zero matches outside this finding.

Suggested fix

Recognize "mcp_tool_use" as an additional call-type alongside "server_tool_use" when populating the call-tracking map (the existing suffix-based result matching already handles "mcp_tool_result" correctly once a matching call is registered), and add a test mirroring the existing server_tool_use test for the MCP connector block pair.

Lenguaje dominante
Java
Estrellas
21
Forks
5
Merge medio
1 d 1 h
PR fusionados (30 d)
5

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 braintrustdata/braintrust-sdk-java

Todos los issues de braintrustdata/braintrust-sdk-java

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.