/**
 * GENERATED — DO NOT EDIT BY HAND.
 *
 * Source: schemas/qar/qar-tools-catalog.json
 * QAR commit: c0157c5c4aaa9304910c6be075e81d253f15c763
 * QAR ref: c0157c5c4aaa9304910c6be075e81d253f15c763
 * Fetched: 2026-10-07
 *
 * Edit the upstream Pydantic models in qodo-ai/qodo-agent-runtime,
 * re-run `python scripts/export-schemas.py` there, bump
 * schemas/qar/.qar-version + the vendored JSON files, then
 * `npm run codegen:qar` regenerates this file.
 */
/**
 * The ``GET /v1/tools`` response document.
 *
 * ``catalog_version`` is the catalog's content-version hash and doubles
 * as the ETag, so an ``If-None-Match`` revalidation maps a hit to
 * ``304``. ``tools`` is sorted by ``(toolset, name)`` — deterministic so
 * a client diffing two fetches sees only real changes.
 */
export interface ToolCatalog {
    catalog_version: string;
    tools: ToolCatalogEntry[];
}
/**
 * One managed tool as a discovery client sees it.
 *
 * The wire projection of :class:`~qar.managed_tools.ManagedToolSpec`:
 * exactly the fields the catalog's content hash keys on, so a client
 * caching by ETag re-fetches iff one of them changed. ``requires_bearer``
 * renames the internal ``requires_principal_bearer`` to the
 * consumer-facing term — whether the caller must supply the Qodo bearer
 * for this tool's upstream.
 */
export interface ToolCatalogEntry {
    description: string;
    mutating: boolean;
    name: string;
    parameters: {
        [k: string]: unknown | undefined;
    };
    requires_bearer: boolean;
    toolset: string;
}
//# sourceMappingURL=qar-tools-catalog.d.ts.map