tool-discovery

You can list available tools by enumerating a given tool directory and registry, which returns structured metadata including name, version, status, riskLevel, and requiresApproval across core, provider, and user-created tools.

Discovering user-created tools involves scanning the tool registry to identify entries and inspect their associated risk levels. It filters for approved tools and non-critical risk levels, returning metadata like executionType and approvedBy for governance.

Yes, you can audit tool lifecycles by checking statuses like draft, approved, or rejected. The tool discovery process handles incomplete tool lifecycles with clear indicators, ensuring you understand the current state of each registry entry.

Tool discovery works across core, provider, and user-created registries simultaneously to consolidate scattered tools. It identifies and enumerates all tools present in a given directory, returning results in a consistent schema for unified visibility.

Incomplete tool lifecycles appear when registry entries lack full approval or rejection metadata. The discovery process handles these by providing clear indicators within the returned structured metadata, showing exactly what information is missing.