ChatGPTClaudeGrok / X / CursorGemini

DeepSeek Harness Tool Catalog: How to Read a Tool Schema

Concepts & ArchitecturePublished 2026-11-18Author: DeepSeek Plugin Market
DeepSeek HarnessDSH plugintool catalogTool Schemaexecution pipeline
The DeepSeek Harness tool catalog maps a tool name to its package, dependencies, write impact, aliases, and schema. Learn to look up a tool instead of guessing.

The DeepSeek Harness tool catalog is not just a list; it is a reverse lookup from the name the model sees back to the package, dependencies, write impact, and aliases. The English source is generated by starting each tool plugin in a real context and reading ctx.tools.schemas(), while the Chinese side is maintained as a reviewed counterpart (source). Knowing how to read it shortens “why does the model not use this tool?” by a lot.

DeepSeek Harness: What the catalog covers

It lists model-facing tools from published plugins, not every function. The scope is packages/*/tool-* started with default config; demo tools under examples/ are excluded (source).

Three scope details matter:

  1. Model-facing only — internal helpers and service methods are absent.
  2. Default config — when a required config field has no default, the generator picks a branch and records it.
  3. Names can be load-time config — for example, tool-subagent has a toolName; a deployment may provide a different or extra name.

The catalog is a snapshot of the product default, not a live list of what your machine enabled. To know whether a deployment has a tool, also check the profile and plugin loading.

Completeness is guarded by verify-tool-catalog, which globs every packages/*/tool-*; a missing package fails the check. New tools are unlikely to vanish from the docs, but they can still be absent from your deployment because config did not enable them.

DeepSeek Harness: Reading the package mapping

The mapping row has six columns: package, model-visible name, dependencies, write impact, aliases, and deployment notes. Each answers a different question (source):

ColumnQuestionDebug use
PackageWho provides it?Find source and version
Model nameWhat does the model see?Search prompts and logs
DependenciesWhich ctx capabilities does it need?Explain why it did not register
Write impactWhich events or state does it touch?Assess permissions and side effects
AliasesIs there a second name?Explain one tool, two names
Deployment notesDefault behavior and limitsDecide whether config must change

Start with dependencies. A missing tool is often a missing service; lsp needs a provider, and terminal tools are opt-in. When dependencies are not met, the tool may not register at all rather than register and fail.

Then read write impact. It tells you whether the tool produces tool/call, tool/result, fs/*, job/*, or other events, which decides its place in permissions, audit, and replay.

Finally read deployment notes. The same tool can behave differently across profiles: bash exposes run_in_background only when a job registry is present.

DeepSeek Harness: The four parts of a tool schema

Read name, description, parameters, and output. They answer what it is called, when to use it, how to fill it, and what it returns. (source)

  • name — the identifier the model calls; renaming affects prompts, logs, and existing calls.
  • description — the model's only clue for when to use it; vague text gets ignored.
  • parameters — JSON Schema shape, required keys, enums, defaults; the model fills from it.
  • output — the canonical return shape and rendering; it decides programmatic access and UI cards.

For “the model does not use the tool,” read description first, then parameters. A description without a use case is not selected; unclear parameters are filled wrong and abandoned.

For “the tool ran but returned the wrong thing,” read output.schema. A value that does not match is a failure; prose instead of canonical JSON breaks programmatic calls.

The catalog shows the schema under default config. A deployment that changes config can change the shape; Web and desktop may expose different parameters for the same tool name.

DeepSeek Harness: Aliases and configured names

One package can have several model-visible names; the catalog records shipped aliases, and deployments can still rename. The official note: the registered name can be load-time config, such as tool-subagent's toolName; shipped aliases are documented (source).

Two consequences:

  1. Search both package and alias — one name may miss the capability.
  2. Do not hard-code tool names in plugins — a deployment may rename, and the hard-coded name breaks after a profile switch.

An alias is not a duplicate registration; it is another entry to the same capability. If two names point to one package, check whether they share a schema. Shared means alias; different means two tools.

When the model calls an unfamiliar name, search the alias column, then the package. Only after both fail consider a third-party custom tool.

DeepSeek Harness: Three reasons a tool is absent

The catalog has a record, but your deployment does not, for three usual reasons. In order (source):

  1. Package not loaded — the profile or bundle does not mount it; check the graph.
  2. Config off — the tool is opt-in, such as the terminal tools; read deployment notes.
  3. Runtime dependency missing — lsp without a provider, image tools without attachments; the tool may not register or may return a structured error.

The checks differ: package presence, config values, and runtime capability. Do not use one method for all three.

There is also a “looks absent” case: the name was configured to something else. It is not missing; it was renamed. Check aliases and deployment notes.

Record “catalog yes, current no” before hunting logs. Confirm loading first; searching logs for a name that never registered is wasted effort.

DeepSeek Harness: A lookup exercise

Walk one real tool name end to end. Use glob (source):

  1. Search the name column — find glob; grep shares the row.
  2. Read the package — @deepseek-ai/dsh-tool-fs-search.
  3. Read dependencies — ctx.subprocess, bundled ripgrep, no shell.
  4. Read write impact — tool/call and tool/result, no extra persistent event.
  5. Read deployment notes — over-limit results can go to ctx.spillStore; co-located deployments can read the locator.

Five steps explain why no host rg is needed, why there is no run_in_background, and where the full list goes when results exceed the cap.

The existing dsh-tool-pipeline-explained covers the execution pipeline and develop-tool-execute-contract covers writing a tool; this article covers the official catalog lookup. Use all three and tool problems stop being guesswork.

ChatGPTClaudeGrok / X / CursorGemini

FAQ

Does the DeepSeek Harness tool catalog list every tool or only default-enabled ones?

The DeepSeek Harness tool catalog lists model-facing tools from published plugins, each started with default config. A required config without a default records which branch the generator chose.

Why does a DeepSeek Harness tool name sometimes differ from its package name?

The DeepSeek Harness tool name can be load-time config, such as subagent's toolName. The catalog records shipped aliases, but a deployment may still use a different or extra name.

Do DeepSeek Harness glob and grep go through a shell?

DeepSeek Harness does not work that way. DeepSeek Harness glob and grep run the bundled ripgrep through ctx.subprocess as ordinary foreground calls, without a shell and without requiring rg on the host.

When does the DeepSeek Harness lsp tool return an error?

The DeepSeek Harness lsp tool requires a registered provider. Without one, a query returns a structured LSP_UNAVAILABLE error instead of changing the schema or failing silently.

Related Terms

tool catalog
The tool catalog is the generated DeepSeek Harness list of model-visible tools, including package, dependencies, write impact, aliases, and schema.— DeepSeek Harness reference - Tool schema catalog
tool package mapping
Tool package mapping is the catalog table that maps a model-visible tool name to its plugin package and service seam.— DeepSeek Harness reference - Tool schema catalog
tool alias
A tool alias is another model-visible name shipped for the same package; a deployment may also provide a different name through config.— DeepSeek Harness reference - Tool schema catalog
tool absence
Tool absence means a tool exists in the catalog but not in the current deployment, usually because the package is not loaded, config is off, or a runtime dependency is missing.— DeepSeek Harness reference - Tool schema catalog

Sources