b3aedf62cd
The Tools screen mounts the Results panel only once a call has produced a result, but the panel's zero-content branch rendered "No results yet" — the same wording it would use before anything had run. An empty `content` array with no `structuredContent` is a legal `CallToolResult`, so a call that had plainly completed reported itself as a call that never happened. That reads worst after a multi-round-trip (MRTR) sequence, which is how it was reported: the user answers one or more embedded elicitations, watches the Protocol tab group the exchange and mark it COMPLETE, and is then told there are no results yet. Nothing was lost — the result was stored and rendered; the panel simply had no wording for "completed, returned nothing". The panel now renders an "Empty result" alert saying the call completed and returned no content. This is the remaining half of the same gap #1908 closed for `structuredContent`-only results. test-servers: new `mrtr_empty` preset (`createMrtrEmptyResultTool`) — one elicitation round, then a complete result with `content: []` and no `structuredContent` — added to `mrtr-showcase-http.json` so the shape is reproducible by hand. README documents it. Signed-off-by: Cliff Hall <cliff@futurescale.com> Signed-off-by: cliffhall <cliff@futurescale.com>
21 lines
450 B
JSON
21 lines
450 B
JSON
{
|
|
"serverInfo": {
|
|
"name": "composable-mrtr-showcase",
|
|
"version": "1.0.0"
|
|
},
|
|
"tools": [
|
|
{ "preset": "echo" },
|
|
{ "preset": "mrtr_confirm" },
|
|
{ "preset": "mrtr_two_step" },
|
|
{ "preset": "mrtr_sample" },
|
|
{ "preset": "mrtr_roots" },
|
|
{ "preset": "mrtr_edge" },
|
|
{ "preset": "mrtr_empty" },
|
|
{ "preset": "mrtr_loop" }
|
|
],
|
|
"transport": {
|
|
"type": "streamable-http",
|
|
"port": 3111,
|
|
"modern": true
|
|
}
|
|
}
|