A list load that failed — a transport error, or a result the SDK's era codec rejects as invalid — reported nothing. The connect-time refresh is fired with no caller to await it (`void this.refresh()`), so its rejection became an unhandled rejection: the header said "Connected", the panel rendered an empty list indistinguishable from a server that has none, and the failed exchange showed in the Protocol panel as a clean success. Two surfaces now tell the truth: - ManagedListState records the failure as observable state (`getError` + an `errorChange` event) and still re-throws, so App's auth-recovery wrapper keeps working. The four `useManaged*` hooks expose it via a shared `useManagedListError`, and the Tools/Prompts/Resources sidebars render a `ListLoadError` alert with the reason and a Retry. - A response the client refused is attributed back to its Protocol entry (`markResponseRejected` → `responseRejected` → `MessageEntry.clientError`), which now renders an Error status and a "Rejected by the Inspector" alert rather than the green resultType badge alone. The SDK gives no request id with a decode failure, so the id is recovered by correlation; see the comment on `markResponseRejected` for why that is exact. Also stops `listAllTools` from dropping a failing excluded-tools walk on the floor — it stays non-fatal but is logged. Closes #1953 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SW1p8E2uiyyLx4RKwrwSrt
98 lines
3.7 KiB
TypeScript
98 lines
3.7 KiB
TypeScript
import { useState, useEffect, useCallback } from "react";
|
|
import type { InspectorClientProtocol } from "../mcp/inspectorClientProtocol.js";
|
|
import type { ManagedToolsState } from "../mcp/state/managedToolsState.js";
|
|
import type { ManagedToolsStateEventMap } from "../mcp/state/managedToolsState.js";
|
|
import type { Tool } from "@modelcontextprotocol/client";
|
|
import type { TypedEventGeneric } from "../mcp/typedEventTarget.js";
|
|
import { useManagedListError } from "./useManagedListError.js";
|
|
|
|
export interface UseManagedToolsResult {
|
|
/**
|
|
* The last fetch's failure (transport error, or a result the SDK codec
|
|
* rejected), or `null` when it succeeded. Includes the connect-time load,
|
|
* whose failure has no caller to surface it (#1953).
|
|
*/
|
|
error: Error | null;
|
|
tools: Tool[];
|
|
/** True when a `tools/list_changed` arrived since the last user refresh. */
|
|
listChanged: boolean;
|
|
refresh: () => Promise<Tool[]>;
|
|
/**
|
|
* Acknowledge the list-changed indicator without fetching the aggregate.
|
|
* Used by the paginated Refresh path, which reloads page 1 of the paged
|
|
* store (bypassing this hook's `refresh`) but must still clear the indicator
|
|
* the managed state lit on `list_changed` (#1721).
|
|
*/
|
|
clearListChanged: () => void;
|
|
}
|
|
|
|
/**
|
|
* React hook that subscribes to ManagedToolsState and returns tools + refresh.
|
|
*/
|
|
export function useManagedTools(
|
|
client: InspectorClientProtocol | null,
|
|
managedToolsState: ManagedToolsState | null,
|
|
): UseManagedToolsResult {
|
|
const [tools, setTools] = useState<Tool[]>(
|
|
managedToolsState?.getTools() ?? [],
|
|
);
|
|
const [listChanged, setListChanged] = useState<boolean>(
|
|
managedToolsState?.getListChanged() ?? false,
|
|
);
|
|
|
|
useEffect(() => {
|
|
if (!managedToolsState) {
|
|
setTools([]);
|
|
setListChanged(false);
|
|
return;
|
|
}
|
|
setTools(managedToolsState.getTools());
|
|
setListChanged(managedToolsState.getListChanged());
|
|
const onToolsChange = (
|
|
event: TypedEventGeneric<ManagedToolsStateEventMap, "toolsChange">,
|
|
) => {
|
|
setTools(event.detail);
|
|
};
|
|
const onListChangedChange = (
|
|
event: TypedEventGeneric<ManagedToolsStateEventMap, "listChangedChange">,
|
|
) => {
|
|
setListChanged(event.detail);
|
|
};
|
|
managedToolsState.addEventListener("toolsChange", onToolsChange);
|
|
managedToolsState.addEventListener(
|
|
"listChangedChange",
|
|
onListChangedChange,
|
|
);
|
|
return () => {
|
|
managedToolsState.removeEventListener("toolsChange", onToolsChange);
|
|
managedToolsState.removeEventListener(
|
|
"listChangedChange",
|
|
onListChangedChange,
|
|
);
|
|
};
|
|
}, [managedToolsState]);
|
|
|
|
const error = useManagedListError(managedToolsState);
|
|
|
|
const refresh = useCallback(async (): Promise<Tool[]> => {
|
|
if (!managedToolsState || !client) return [];
|
|
// A user-initiated refresh acknowledges the change — clear the indicator
|
|
// BEFORE awaiting the fetch, not after. If a `tools/list_changed` arrives
|
|
// mid-fetch, the state re-sets the flag (and auto-refreshes); clearing
|
|
// afterward would wipe that genuinely-new signal and the user would miss
|
|
// it. Clearing up front acknowledges only the change in hand.
|
|
managedToolsState.clearListChanged();
|
|
// A user-initiated refresh forces a cache-bypassing round trip
|
|
// (`cacheMode: "refresh"`) so a modern server's `ttlMs`-cached list can't
|
|
// return stale — and re-stores the fresh aggregate.
|
|
const next = await managedToolsState.refresh(undefined, "refresh");
|
|
setTools(next);
|
|
return next;
|
|
}, [client, managedToolsState]);
|
|
|
|
const clearListChanged = useCallback(() => {
|
|
managedToolsState?.clearListChanged();
|
|
}, [managedToolsState]);
|
|
|
|
return { tools, error, listChanged, refresh, clearListChanged };
|
|
}
|