diff --git a/nix/module.nix b/nix/module.nix index 2896664..35ee3eb 100644 --- a/nix/module.nix +++ b/nix/module.nix @@ -989,8 +989,8 @@ in { # to declare. environment.systemPackages = lib.mkIf cfg.mcp.enable [ cfg.mcp.package ]; - # A warning and not an assertion: eighteen of the twenty-one tools and six - # of the eight resources need the broker, and an agent handed them against + # A warning and not an assertion: twenty of the twenty-three tools and + # seven of the ten resources need the broker, and an agent handed them against # a machine where it is off gets exit 5 from every one of them -- which is # a true answer, badly timed. The frame tools are genuinely useful on their # own, so this is a thing worth saying rather than a thing worth refusing. diff --git a/src/hhstream_mcp/tools.py b/src/hhstream_mcp/tools.py index 8c83df0..f8ea5eb 100644 --- a/src/hhstream_mcp/tools.py +++ b/src/hhstream_mcp/tools.py @@ -31,7 +31,7 @@ with an ``action`` enum. Three reasons, in order of weight: 3. ``readOnlyHint`` is per tool and is still a real distinction among what is left: ``shot`` reads, ``session_kill`` destroys, ``record`` writes a file. -The cost is twenty-one tools in one listing, and :data:`TOOLSETS` is the lever +The cost is twenty-three tools in one listing, and :data:`TOOLSETS` is the lever for a client that cannot afford them all. It is paid back by the names being the CLI's own: an agent that has read ``hhstream session --help``, or this repository's README, already knows what ``session_touch`` is, and a transcript