AI Agent Hub
Back to plugins
🧩

dsh-tool-visibility

admin-security Updated 2026.08.26

Run the following command in DeepSeek Harness:

dsh plugin install rayfalling/dsh-tool-visibility

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install rayfalling/dsh-tool-visibility in DeepSeek Harness to install this plugin; source: https://github.com/rayfalling/dsh-tool-visibility

About this plugin

As the number of tool-centric plugins grows, each model request carries an ever-expanding list of tool schemas, and definitions irrelevant to the current task silently consume precious context window. dsh-tool-visibility solves exactly that: it lets you toggle individual tool schemas on or off, stripping unnecessary definitions from every step of the request and reclaiming usable token space.

The plugin ships two control surfaces. On the browser side, a dedicated settings page (Settings → Tool Injection Control) lists every tool with checkboxes, supports name-prefix grouping, search, and bulk toggling, and persists the hidden set to a local JSON state file that is restored automatically on restart. On the model side, the tool_visibility tool exposes list, hide, show, and reset operations so you can adjust visibility mid-conversation. Under the hood it prefers the framework-native ctx.tools.restrict mechanism—hidden tools are excluded from context entirely and any call returns UNKNOWN_TOOL—falling back to a system-prompt assembly filter when restrict is unavailable, so the feature always works.

If you run a stack of pure tool plugins whose schemas number in the dozens per request, or you want a specific preset to expose only the tools relevant to its task, this plugin lets you raise context efficiency at minimal overhead.

Use Cases

  • Too many tool schemas bloat each request; selectively hide irrelevant tools to reclaim context
  • A specific preset should only expose tools relevant to its current task
  • Quickly toggle tool visibility from a settings page without modifying any plugin code

Best For

  • Developers running many tool-centric plugins with dozens of schemas per request
  • Advanced DSH users who need fine-grained control over model context
  • Teams that configure different tool visibility per preset