Skip to main content
Glama
Sign In
dsh-baton

dsh-baton

by JialaoLiu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

dsh_call

Destructive

Call a dsh-baton tool by name, including ones added by an update without restart, and pass arguments as its schema describes. Unknown names return available tools and input schemas.

Instructions

Call a dsh-baton tool by name, for a tool this conversation does not list (dsh-baton was updated without a restart; the update note names it). Runs the same code as a direct call, so it can do whatever that tool does. An unknown name changes nothing and returns the tools with their input schemas.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTool name, e.g. dsh_send or a tool added by an update
argumentsNoArguments for that tool, as its input schema describes them (see the list returned for an unknown name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.4

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already mark this as destructive and non-idempotent, and the description adds important context: it runs the same code as a direct call, can do whatever that tool does, and an unknown name changes nothing and returns tool schemas. That is strong disclosure for an arbitrary dispatcher, though it cannot enumerate target-specific side effects.

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

Conciseness5/5

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

The description is three tight sentences with no waste. The scoping condition, behavioral note, and unknown-name behavior are front-loaded and easy to scan.

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?

For a generic dispatcher with no output schema, the description covers when to use it, that it behaves like a direct call, and how invalid names are handled. Success output remains implied rather than stated, but the core information needed to invoke it safely is present.

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 schema already explains both 'name' and 'arguments,' including the unknown-name return path. The description reinforces that the call is by name and that arguments follow the target tool's schema, but it adds little beyond the structured parameter documentation.

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 states a specific verb and resource: 'Call a dsh-baton tool by name.' It immediately scopes the purpose to tools this conversation does not list, which distinguishes it from direct calls and the listed sibling tools.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use condition: an unlisted tool from an update without restart. It also names the direct-call alternative and explains the fallback behavior for an unknown name, so an agent knows both when and when not to use it.

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

Deploy Server

Other Tools