The ``annotations.py`` module ============================= .. py:module:: ansys.fluent.mcp.common.host.annotations Summary ------- .. py:currentmodule:: annotations .. tab-set:: .. tab-item:: Functions .. list-table:: :header-rows: 0 :widths: auto * - :py:obj:`~annotations_for` - Return the behavior hints for a tool. .. tab-item:: Constants .. list-table:: :header-rows: 0 :widths: auto * - :py:obj:`~READ_ONLY` - Reads state or builds code without changing anything. * - :py:obj:`~ADDITIVE` - Adds or attaches state without overwriting anything; safe to repeat. * - :py:obj:`~OVERWRITE` - Overwrites values or lifecycle state; repeating with the same arguments is harmless. * - :py:obj:`~DESTRUCTIVE` - Arbitrary or irreversible mutation; confirm first and never retry blindly. * - :py:obj:`~LEAF_TOOL_ANNOTATIONS` - Hints for every tool the shared leaf base and the solve leaf register. Description ----------- MCP tool annotations (behavior hints) for the leaf tool surface. MCP hosts (VS Code Copilot, Claude Desktop, Cursor) read ``readOnlyHint``, ``destructiveHint`` and ``idempotentHint`` to decide which calls can run without confirmation and which ones must not be retried blindly. Each tool is classified by its worst-case action. Lifecycle tools named ``manage_