Skip to main content
Glama

Check DSH bridge health

dsh_health_check
Read-onlyIdempotent

Checks local DSH CLI, headless profile, DeepSeek route, write authorization, and credential-file presence without reading credentials; optionally runs a tiny live model call to verify connectivity.

Instructions

Check the local DSH CLI, headless profile, DeepSeek account route, local write authorization, and credential-file presence without reading credentials. Set probe=true to make a tiny live DSH model call and verify the model connection. Does not modify files.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dsh_health_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
probeNoWhen true, run a small real DSH model call (uses a small amount of DeepSeek usage).

Output Schema

NameRequiredDescriptionDefault
okYes
dshYes
bridgeYes
securityYes
warningsYes
checked_atYes
model_probeYes
surface_noteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the burden is lower. The description adds genuinely non-obvious context: it inspects credential-file presence without reading credentials, and probe=true incurs real DeepSeek usage cost. "Does not modify files" largely restates destructiveHint=false and is the weakest sentence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what is checked, followed by the opt-in probe behavior and the no-modification guarantee. Efficient overall, but the closing "Does not modify files" is redundant against the annotations and could be dropped without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the single optional parameter is fully covered. What it checks and what the probe costs are both stated; only prerequisites (auth or environment requirements for the bridge) are left implicit, which is minor for a self-diagnosing health tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one parameter at 100% schema description coverage, the schema already documents probe's default and its cost. The description adds only a marginal nuance — that probe verifies the model connection — which the schema's "small real DSH model call" mostly covers. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("Check") and enumerates exactly what is verified: local DSH CLI, headless profile, DeepSeek account route, local write authorization, and credential-file presence. It also distinguishes itself from the task-oriented siblings by naming the scope as a readiness/diagnostic probe rather than a task operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly explains the one decision point an agent faces — leaving probe at its default false for a cheap static check versus setting probe=true for a live model call that consumes DeepSeek usage. There is no explicit statement of when this tool should be preferred over the sibling task tools, but the diagnostic purpose makes that implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.