Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_dispatcher_ensure_started

Idempotent

Ensures exactly one callback dispatcher runs for the active repository and selected coordinator target, preventing duplicate threads after handshakes or target switches.

Instructions

Idempotently ensure exactly one callback dispatcher is running for the active repository, bound to the currently-selected coordinator target (B857). Called by the VS Code extension after every MCP handshake (activation, tab-deserialization, reload) and after an explicit coordinator-target switch -- never starts a second thread and never marks an uninitialized repository as degraded.

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": "aiworkhub_dispatcher_ensure_started"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description's job is to add context, and it does: never starts a second thread, and never marks an uninitialized repository as degraded. These are real behavioral guarantees an agent could not infer from the structured fields. It stops short of describing failure modes or what the spawned dispatcher does.

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 sentences, front-loaded with the core action and scope before the invocation context. The internal ticket marker '(B857)' is noise an agent cannot use, and the parenthetical activation list is dense, but nothing else is wasted.

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, an output schema, and full annotation coverage, the remaining burden is purpose, call site, and guarantees — all present. Only error/retry behavior when dispatcher startup fails is unaddressed.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline applies. The description usefully explains that the active repository and coordinator target are implicit inputs resolved from ambient state, which is the only parameter-like context available.

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?

States a specific verb and resource (ensure a callback dispatcher is started) plus the precise scope: exactly one, for the active repository, bound to the currently-selected coordinator target. An agent can distinguish this from the sibling dispatcher_health / dispatcher_stop / dispatcher_watchdog without opening any schema.

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?

Explicitly names the invocation context: after every MCP handshake (activation, tab-deserialization, reload) and after an explicit coordinator-target switch. It does not name sibling alternatives or a when-not-to-call condition, so it falls short of a 5, but the intended call site is unambiguous.

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