List all configured Swagger documentation sources and their cache status.

For each service, returns:

• name: Service name (from config, or auto-read from projectName).

• fetchedAt: Last cache time (null means not yet loaded).

• totalInterfaces: Total interface count (shown when loaded).

• modules: Module list.

Use this before calling swagger_search_api to discover which services are available.

Search API interfaces in the internal Swagger documentation.

Searches by keyword across interface name, description, path, and module name. Optionally filter by HTTP method and service.

Parameters:

• keyword (required): Search keyword, e.g. "登录", "user", "/api/order". Chinese is supported.

• method (optional): HTTP method filter, e.g. "GET", "POST".

• source (optional): Service name filter, taken from swagger_list_sources results.

• include_deprecated (optional): Whether to include deprecated interfaces. Default false.

• limit (optional): Maximum number of results. Default 20.

Response: Each matched interface includes: service name, module name, HTTP method, full path, interface name, description, status.

Examples:

• Search login interfaces: keyword="登录"

• Search POST interfaces: keyword="用户", method="POST"

• Search within a specific service: keyword="order", source="订单服务"

Get full details of a single API interface, including all parameter definitions and response examples.

Parameters:

• source (required): Service name, from the [service name] returned by swagger_list_sources or swagger_search_api.

• method (required): HTTP method, e.g. "GET", "POST".

• path (required): Full interface path, e.g. "/qmAuthorityCenter/systemFun/initPerformanceSolution".

Response includes:

• Basic interface info (name, description, status, Content-Type).

• Full definitions for Query / Path / Header / Form / Body parameters (name, type, required, description). Required column: "是" = required, "否" = optional, "?" = platform metadata is ambiguous (checkType=1 with no error message — cross-check with backend code or treat as optional).

• Sub-fields of nested Object parameters.

• Response results (Demo JSON + output field table).

• Mock response field table.

Force-refetch Swagger documentation data and update the cache.

Use this after the documentation has been updated (interfaces added or modified) to fetch the latest data.

Parameters:

• source (optional): Service name. Omit to refresh all services.

Returns: Refresh results, including success/failure status and updated interface counts.