Skip to main content
Glama

faf_setup

Installs a SessionStart hook for fresh .faf context each Claude Code session. Previews settings before writing; preserves existing hooks. Use confirm:true to write, remove:true to uninstall.

Instructions

Install the native SessionStart hook — every Claude Code session in this project starts with fresh .faf context. Shows the exact settings JSON first (preview); writes only with confirm: true. Non-destructive: existing settings and hooks are preserved. remove: true uninstalls exactly the faf hook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoProject path. Defaults to the current project context.
confirmNoActually write the hook into .claude/settings.json. Without it, faf_setup only previews.
removeNoRemove the faf SessionStart hook (and only it) from .claude/settings.json.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhat faf_setup did
settingsPathYesThe settings file involved
hookCommandNoThe command the SessionStart hook runs
settingsNoThe full settings object as written (or as it would be written in preview)
messageYesHuman-readable summary
Behavior5/5

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

The description adds value beyond annotations by detailing non-destructive behavior, preview-first workflow, and exact removal. It aligns with destructiveHint=false and clearly explains the confirm flag's role.

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 efficient sentences plus a third for remove. Front-loaded with purpose, every sentence adds unique value. No waste.

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?

Covers all aspects of setup, preview, write, remove, and non-destructive nature. With output schema present, return values are not needed. Complete for a setup tool.

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

Parameters4/5

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

Schema already describes all 3 parameters at 100% coverage. The description adds context: preview behavior for confirm, exact removal for remove, though schema descriptions are already clear.

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 tool installs a native SessionStart hook, contrasting with siblings by focusing on setup, preview, and removal. It uses specific verbs and resources.

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 confirm:true versus preview, and when to use remove:true. It provides context for the tool's role in project sessions but does not explicitly mention alternatives or when not to use.

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/Wolfe-Jam/claude-faf-mcp'

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