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

workbuddy-subagent-bridge

by BenjaminNH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

workbuddy_session_close

Close a running task session and mark it as completed by providing the task ID.

Instructions

Close the local ACP process and mark the task completed.

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

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Describes the core effect (closing the process and marking the task completed) but does not disclose side effects, reversibility, or error states. With no annotations provided, the description carries the burden and only partially covers it.

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?

Single sentence with no redundant wording. The verb and object are front-loaded, and every word earns its place.

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

Completeness3/5

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

Adequate for a simple close operation but lacks usage context and parameter clarification. It does not explain how it relates to other session tools or what state the process should be in, leaving some ambiguity for an agent.

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

Parameters2/5

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

Does not explain the taskId parameter beyond its existence. Since schema coverage is 0%, the description should clarify that taskId identifies the task to close, but it omits this entirely, leaving the agent to infer its role.

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 exactly what it does: closes the local ACP process and marks the task completed. This clearly distinguishes it from sibling tools like session_start or session_send, and the verb-resource pair is specific.

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?

Offers no guidance on when to use this tool versus alternatives like session_cancel or session_send. It does not mention prerequisites, ordering, or conditions that would make this the correct choice.

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