Skip to main content
Glama

Inspect the DSH bridge environment (read-only)

dsh_get_capabilities
Read-onlyIdempotent

Reports read-only DSH paths, versions, pinned model route drift, credential presence, SDK methods, workspace bounds, and limits so clients can verify capabilities without a model request.

Instructions

Read-only. Reports the community-edition DSH paths and versions, the pinned model route and any drift from the live desktop profile, credential presence (never its value), the SDK methods actually present in the pinned runtime, workspace bounds and the honest limit list. Starts no model request.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.8

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, idempotent, not open-world), and the description goes beyond them with two genuinely additive guarantees: no model request is issued, and credentials are reported only as present/absent, never as values. "Honest limit list" and drift-vs-live-profile also hint at what the report may flag as divergent, though the shape of the output is not described.

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?

Front-loaded with "Read-only." and then a single dense sentence that enumerates report contents with no filler. The one cost is that the long comma-separated list is hard to scan and could have been split into a short bulleted inventory.

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 zero params and no output schema, the description carries the burden of explaining what comes back, and it does so by enumerating the reported items plus privacy and no-model-call caveats. Minor gap: it does not say how the report is shaped or whether drift/limits are reported as structured fields or free text.

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

Parameters4/5

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

Zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The description correctly implies a parameterless call by describing a fixed report payload.

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?

States the verb ("reports") and enumerates the exact resource contents: paths/versions, pinned model route and drift, credential presence, SDK methods, workspace bounds, limit list. That content profile is unmistakably distinct from siblings like dsh_get_events or dsh_get_task, though the description never names a sibling to contrast with explicitly.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not statement, and no alternative is named. Usage is only implied: "Read-only" plus "Starts no model request" signals it is a cheap, safe pre-flight probe, but the agent must infer that this is the tool to call before task/event operations.

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