Skip to content

v0.5.0

Choose a tag to compare

View all tags
@silversurfer562 silversurfer562 released this 12 Apr 03:38
· 25 commits to main since this release
v0.5.0
656af83

MCP layer catches up to the 0.4 HelpEngine public API. Everything added to the Python API in 0.4 is now reachable from an MCP client.

Added

  • lookup_simpler MCP tool — step a topic one depth level back down, mirroring HelpEngine.simpler().
  • lookup_list_topics MCP tool — flat slug enumeration optionally filtered by type (concepts, tasks, references, …).
  • lookup_search MCP tool — fuzzy slug search returning ranked {slug, score} hits.
  • lookup_suggest MCP tool — "did you mean" slug suggestions.
  • lookup_reset now accepts an optional topic parameter to clear a single topic instead of the full session.
  • lookup_status now returns the full per-topic depth map (topics) and LRU order (order) alongside the legacy last_topic / depth_level fields.
  • "json" is now an accepted renderer across every MCP tool that renders content.
  • Public attune_help.engine.VALID_RENDERERS constant so downstream code can derive allowlists from the same source the engine uses.

Fixed

  • Renderer allowlist drift between HelpEngine and the MCP layer. The handler and schema enum now both derive from engine.VALID_RENDERERS, so adding a renderer automatically propagates to MCP.
  • MCP lookup_reset previously wrote the legacy (pre-0.4) session schema, bypassing per-topic history. It now delegates to HelpEngine.reset().
  • MCP tool count assertion was hardcoded — now uses the dispatch table as the source of truth.

Changed

  • Nothing breaking. All existing MCP tool names and response shapes are preserved. New fields on lookup_status are additive; the topic parameter on lookup_reset is optional.

PyPI: https://pypi.org/project/attune-help/0.5.0/

Assets 2
Loading