Skip to main content
Glama
linanwanttodo

spec-driver-mcp

create-hook

Register automation hooks to trigger AI actions when spec workflow events occur, such as automatically marking tasks complete upon completion.

Instructions

Register an automation hook for the spec workflow. Hooks define actions the AI should automatically perform when specific events occur. Events: on-requirements-confirmed, on-design-confirmed, on-tasks-confirmed, on-task-completed, on-implementation-done, on-spec-phase-change, on-user-request-change, manual

Example: when a task is completed (on-task-completed), auto-run update-task to mark it [x].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesUnique hook name (e.g. auto-mark-completed)
eventYesEvent that triggers this hook
descriptionYesShort description of what this hook does
instructionsYesDetailed instructions for the AI to execute when triggered
Behavior4/5

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

Despite no annotations, the description discloses the action (registration), events, and example; but lacks details on persistence or limits.

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?

Concise, front-loaded with purpose, followed by explanation, events list, and example; no wasted words.

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?

Provides necessary context for a registration tool, but could clarify manual event vs automatic, and return behavior.

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

Parameters5/5

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

Schema coverage is 100% and the description adds meaning by explaining each parameter, listing events, and providing an example.

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 the verb 'Register' and resource 'automation hook', and distinguishes from siblings like delete-hook, list-hooks, run-hooks.

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?

The description explains when to use (to automate actions on events) and provides examples, but does not explicitly contrast with alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/linanwanttodo/spec-driver-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server