Skip to main content
Glama

workbuddy_start_development

Delegates a Git implementation task to WorkBuddy, requires the committed spec in the repository, and pushes a review branch for inspection without merging.

Instructions

Delegate a Git implementation task to WorkBuddy. The specification must already be committed and reachable in the repository. This tool instructs WorkBuddy to push a review branch and never merge it.

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": {
      "repositoryUrl": "<repositoryUrl>",
      "workBranch": "<workBranch>"
    },
    "name": "workbuddy_start_development"
  }
}

Input Schema

NameRequiredDescriptionDefault
specPathNo.agent-handoff/SPEC.md
baseBranchNomain
workBranchYes
testCommandNo
repositoryUrlYes
additionalInstructionsNo

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?

With no annotations, the description carries the full burden and does disclose key behavior: the agent pushes a review branch and never merges. That is useful side-effect and safety context. Missing are the operational traits that matter for delegation: whether the call blocks or returns immediately (siblings like workbuddy_wait_for_reply suggest async), what happens on failure, and any auth/remote-permission requirements.

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?

Three short sentences, zero filler, and the core action is front-loaded before the precondition and the safety boundary. Each sentence contributes a distinct fact.

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 mutation tool with no annotations, no output schema, and six undocumented parameters, the description is thin. An agent still cannot tell whether the call is synchronous, what a successful handoff returns, or which parameters control branching and test execution, so the definition is not complete enough for confident invocation.

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?

Schema description coverage is 0% across 6 parameters, so the description must compensate and largely does not. Only specPath is indirectly implied by 'the specification must already be committed'; repositoryUrl, workBranch, baseBranch, testCommand, and additionalInstructions are left entirely to the schema's names, formats, and defaults.

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 a specific verb and resource: 'Delegate a Git implementation task to WorkBuddy.' The named delegate (WorkBuddy) implicitly separates it from the codebuddy_* siblings, though the description never explicitly contrasts the two start_development tools.

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?

Gives a hard precondition for use: 'The specification must already be committed and reachable in the repository.' That is clear context for when the tool applies. It does not name alternatives or say what to do when the precondition fails (e.g., commit the spec first).

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