Parallel tool calling non-deterministic response order results in confused bots

Describe the bug

Copilot harness loses request correlation for parallel tool calls

Summary

The Copilot harness does not preserve a reliable association between parallel tool requests and their responses.

The harness can return parallel responses without the original request, a caller-defined alias, or another usable
correlation value. The agent can then associate a response with the wrong request.

Observed behaviour

The agent sent separate service searches for these filters:

{ "type": ["application"] }
{ "type": ["data-product"] }
{ "type": ["kafka-connect"] }

The responses contained different totals. The harness did not return a request alias or the original request with each response. The agent matched the totals to the wrong filters and reported an incorrect breakdown.

The response position was not a safe correlation method.

Expected behaviour

The harness must preserve the association for every parallel invocation.

The parallel call format can accept an optional caller-defined alias:

{
  "request_alias": "kafka-connect-count",
  "tool": "delivery_platform_search_services",
  "arguments": {
    "type": ["kafka-connect"],
    "environment": "prod"
  }
}

Each response must return the alias and the request:

{
  "request_alias": "kafka-connect-count",
  "request": {
    "type": ["kafka-connect"],
    "environment": "prod"
  },
  "result": {
    "pagination": {
      "total_items": 71
    }
  }
}

The harness must not require response order to match request order.

If the caller does not provide an alias, the harness can return its internal call ID. The internal ID alone is not
enough for semantic correlation. The response must also include the original request or another stable request
description.

Suggested fix

Add request metadata to the parallel tool runner.

The runner must:

1. Accept an optional request_alias for each invocation.
2. Keep the alias with the invocation while the tool runs.
3. Return the alias, original arguments, and result together.
4. Preserve the association when responses complete out of order.
5. Keep aliases out of the arguments sent to the underlying tool API.

The same response envelope can apply to single tool calls for consistent behaviour.

Workaround

I did a poor-mans implementation of the above, by wrapping our server.registerTool function with something that:

• Adds an optional request_alias field to registered tool input schemas.
• Removes request_alias before the tool handler runs.
• Adds the alias to structuredContent.request_alias in the response.
• Extends declared output schemas when they exist.
• Covers JSON, text, generated, and proxied tools.

I also added the following to our instruction file:

• Assign a unique alias to every parallel invocation.
• Put the alias in the actual tool arguments.
• Match responses by alias and exact arguments.
• Run calls sequentially when a tool does not support aliases.
• Treat a response without the expected alias as uncorrelated.

That worked well:

But only works for tools we register.

Affected version

1.0.78

まず、workaround で説明されている parallel tool runner と server.registerTool ラッパーを追跡します。呼び出しメタデータがレスポンスにどのように引き継がれるか、また引数が基盤となるツール API にどのように渡されるかを確認します。呼び出しが順不同で完了しても、エイリアス、元のリクエスト、結果の対応関係が維持され、エイリアスがツール引数として転送されなければ完了です。