Skip to main content
Glama
Sign In
workbuddy-subagent-bridge

workbuddy-subagent-bridge

by BenjaminNH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

workbuddy_session_cancel

Cancel an active WorkBuddy session by supplying its task ID to stop ongoing delegated execution.

Instructions

Cancel the active WorkBuddy session.

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": {
      "taskId": "<taskId>"
    },
    "name": "workbuddy_session_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a destructive action ('cancel') but does not specify side effects, reversibility, authentication requirements, or what happens to the session. This is a significant gap for a mutation tool.

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 a single, short sentence with no filler words. It is front-loaded with the action. While it lacks detail, that is a completeness issue, not a conciseness issue. Every word earns its place.

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

Completeness2/5

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

For a simple tool with one parameter but zero annotation coverage and no output schema, the description is severely incomplete. It fails to explain the taskId parameter, any preconditions, or what 'active' means. An agent cannot reliably call this tool with the provided information.

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

Parameters1/5

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

The input schema has one required parameter, taskId, with no description. Schema description coverage is 0%, so the description must explain what taskId refers to. It does not, leaving the agent to guess what value to provide, which is critical for correct invocation.

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?

The description clearly states the verb 'Cancel' and the resource 'active WorkBuddy session', which is specific. However, it does not distinguish from the sibling 'workbuddy_session_close', which likely has a similar or overlapping purpose. An agent might not know when to use this tool vs the close tool.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'close' or 'send'. There are no conditions, prerequisites, or exclusions mentioned. The description only states the action without any context on when it is appropriate.

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