Search the internal knowledge base for standards, runbooks, and architecture decisions.

Use this tool when an engineer asks about:

• How something should be done (standards)

• How to respond to an incident (runbooks)

• Why an architectural choice was made (ADRs)

Args: query: Free-text search query describing what the engineer is looking for. category: Optional filter — one of "standard", "runbook", or "adr". tags: Optional list of tags to filter by (e.g. ["python", "security"]).

Returns: JSON string with matching documents (summaries) or a not-found message.

Retrieve an internal document by its ID.

Use this after search_internal_docs to get details of a specific document. Document IDs follow the format: STD-001, RUN-002, ADR-003, etc.

Args: document_id: The document identifier (e.g., "STD-001", "RUN-002"). summary: When True, return only a summary (first 500 chars) instead of the full content. Useful for long documents to save context.

Returns: JSON string with the document content (or summary), or an error if not found.

List all available documentation categories with descriptions.

Use this to understand what kinds of documents are available in the knowledge base before searching.

Returns: JSON string with available categories and their descriptions.

List all available tags used across internal documents.

Use this to discover what topics are covered and to refine searches with tag filters.

Returns: JSON string with all available tags sorted alphabetically.

List all documents in the knowledge base, optionally filtered by category.

Use this to get an overview of everything available. For specific questions, prefer search_internal_docs instead.

Args: category: Optional filter — one of "standard", "runbook", or "adr".

Returns: JSON string with document summaries.