Skip to main content
Glama

DeepSeek Harness bridge info

dsh_info

Reports DSH launcher, model route, API-key availability, live SDK runtimes, and tracked runs so you can diagnose failed DSH calls; call it first when a DSH call fails.

Instructions

Report the DSH launcher, model route, API-key availability, live SDK runtimes, and tracked runs. Call this first when a DSH call fails.

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionNoNamed bridge connection from mcp-bridge.json. Omit to use the configured default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. "Report" implies a read-only diagnostic with no side effects, and the list of reported items tells the agent what evidence it will get back. However, it never states outright that nothing is mutated, nor whether the call is safe to repeat or costs anything, which matters for a tool an agent is told to call on failure.

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?

Two sentences, zero filler, and the diagnostic trigger is deliberately placed second as the routing cue. The dense enumeration of reported fields is efficient, though a reader unfamiliar with DSH acronyms has to infer what some items mean.

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?

With no output schema and no annotations, the description has to convey return content itself, and it does so by listing the five categories of reported state. For a one-optional-parameter diagnostic tool that is largely sufficient; only the response shape and whether failures are reported rather than raised are left implicit.

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?

Schema coverage is 100% and the single optional parameter (`connection`) is fully documented in the schema, including the omit-to-use-default behavior. The description adds nothing about connections, so the baseline of 3 is correct.

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

Purpose4/5

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

"Report" is a specific verb and the description enumerates exactly what is reported: launcher, model route, API-key availability, SDK runtimes, tracked runs. That is enough to separate it from siblings like dsh_run or dsh_sessions, which plainly execute or list. The only weakness is reliance on unexplained DSH/SDK jargon, but the resource itself is concrete.

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?

"Call this first when a DSH call fails" gives an explicit, actionable trigger, which is exactly the situation an agent needs routing for. It does not state when *not* to call it or name a competing diagnostic tool, so it stops short of full when/when-not guidance.

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