MeetJSON

Only two tools exist and their high-level split (content processing vs. state/memory) is reasonably clear. However, each tool bundles four to five unrelated operations, so an agent cannot select a specific behavior — it must rely on the tool's internal content detection or on an ambiguous parameter to decide between repair, prune, AST extraction, checkpoint restore, or memory recall.

Both tools follow an identical `meetjson_<noun>` pattern in snake_case with a shared server prefix, which is fully predictable. The convention is uniform even if the suffix nouns ('process', 'state') are vaguer than ideal.

Two tools is far too thin for the surface being exposed: the functions described (syntax repair, array pruning, AST extraction, snapshot save/restore/list, memory store/recall) would naturally be eight or more distinct tools. Each tool is a megatool that forces the agent to guess at hidden modes.

Core capabilities are nominally covered by the two omnibus tools, and the state engine lists save/restore/list plus store/recall. Gaps remain, though: there is no explicit delete/clear for checkpoints or memories, no targeted single-format or single-operation entry points, and no way to run repair or AST extraction without triggering the ambiguous universal pipeline.