Specky

Create Feature Branch

sdd_create_branch

Read-onlyIdempotent

Generates a standardized branch name from SDD conventions and provides a copyable command hint for your terminal. Avoids naming errors and ensures consistency in feature branches.

Instructions

Generates a branch name following SDD conventions and returns a command_hint for creating the branch. Does not execute git commands — the AI client or user runs the command.

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

Input Schema

Name	Required	Description	Default
`spec_dir`	No	Spec directory path (relative to workspace root)	.specs
`base_branch`	No	Base branch to create from	main
`branch_prefix`	No	Branch name prefix (e.g., 'feature/', 'feat/', 'spec/')	feature/
`feature_number`	No	Feature number (zero-padded, e.g. '001')	001

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.4.0-rc.14May 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description confirms non-execution and adds that it returns a command_hint, providing transparency beyond annotations.

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?

Two short sentences that are front-loaded with the core purpose, followed by a critical usage caveat. No wasted words.

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

Completeness5/5

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

Given the tool's low complexity and the absence of an output schema, the description sufficiently explains what the tool does and what it returns. Complete for its purpose.

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?

Input schema has 100% description coverage for all 4 parameters. The description does not add any additional semantic meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 clearly states it generates a branch name following SDD conventions and returns a command_hint. It differentiates from sibling tools like sdd_create_pr by focusing on branch naming rather than PR creation.

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 states it does not execute git commands, guiding the AI to use it for generating commands rather than executing. Could be improved by mentioning when to use this versus other branching tools, but still clear.

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

Deploy Server