tool-design

Included with Lifetime

$97 forever

Design effective MCP tools and Claude Code integrations using the consolidation principle. Fewer, better-designed tools dramatically improve agent success rates. Use when creating MCP servers, designing tool interfaces, optimizing tool sets, or when user mentions 'tool design', 'MCP', 'fewer tools', 'tool consolidation', 'tool architecture', or 'tool optimization'.

Design

What this skill does


# Tool Design Skill

Design effective MCP tools and Claude Code integrations using the consolidation principle.

## Core Insight

**Fewer tools = Higher success rates**

Vercel d0 achieved 80% → 100% success by reducing from 17 to 2 tools. This isn't coincidence—it's architecture.

## The Consolidation Principle

### Why Fewer Tools Work Better

1. **Reduced decision space** - Model selects correct tool more often
2. **Simpler context** - Less instruction text per tool
3. **Better parameter handling** - Focused parameters vs kitchen-sink
4. **Clearer intent** - Tool purpose is unambiguous

### Tool Count Impact

| Tool Count | Expected Success | Example |
|------------|------------------|---------|
| 1-3 | 95-100% | Vercel d0 (2 tools) |
| 4-7 | 85-95% | Focused agent |
| 8-15 | 70-85% | General assistant |
| 15+ | <70% | Kitchen sink |

## What's Included

### Examples (`examples/`)
- **MCP consolidation** - Real before/after tool reduction
- **Grey Haven patterns** - How Grey Haven MCP servers follow consolidation
- **Anti-patterns** - Common tool design mistakes

### Reference Guides (`reference/`)
- **Consolidation guide** - Complete tool reduction methodology
- **MCP best practices** - Naming, parameters, descriptions
- **Decision framework** - When to use tools vs agents vs skills

### Checklists (`checklists/`)
- **Tool audit checklist** - Evaluate existing tool sets
- **New tool checklist** - Before adding a new tool

## Key Patterns

### 1. Architectural Reduction

Before (17 tools):
```
create_file, read_file, update_file, delete_file,
list_directory, search_files, get_file_info,
create_folder, rename_file, move_file, copy_file,
get_permissions, set_permissions, watch_file,
compress_file, decompress_file, calculate_hash
```

After (2 tools):
```
file_operation(action, path, content?, options?)
directory_operation(action, path, options?)
```

**Result**: 80% → 100% success rate

### 2. Parameter Consolidation

Instead of many tools with few parameters, use few tools with structured parameters.

**Before** (5 tools):
```typescript
search_code(query: string)
search_files(pattern: string)
search_in_file(file: string, query: string)
search_directory(dir: string, query: string)
search_with_regex(regex: string)
```

**After** (1 tool):
```typescript
search(options: {
  query: string
  type: 'code' | 'files' | 'content'
  path?: string
  regex?: boolean
})
```

### 3. MCP Fully-Qualified Naming

Use prefixes to prevent collisions and clarify scope:

```
mcp__firecrawl__search          // External MCP
mcp__linear__create_issue       // External MCP
search                          // Claude Code native
```

### 4. Tool vs Agent Decision

| Use Tool When | Use Agent When |
|---------------|----------------|
| Single operation | Multi-step workflow |
| Deterministic result | Judgment required |
| Fast execution (<1s) | Complex reasoning |
| Simple I/O | Context accumulation |

## Grey Haven MCP Integration

Grey Haven uses these MCP servers effectively:

| Server | Tools | Purpose |
|--------|-------|---------|
| firecrawl | 5 | Web scraping, search |
| linear | 12 | Issue/project management |
| playwright | 15 | Browser automation |
| context7 | 2 | Documentation lookup |
| filesystem | 10 | File operations |

### Consolidation Opportunities

Even well-designed MCPs can be wrapped for consolidation:

```typescript
// Instead of exposing all 15 playwright tools
// Create 3 workflow-level tools:

browser_navigate(url, options?)       // Navigate + wait
browser_interact(selector, action)    // Click/type/select
browser_extract(selector, format)     // Screenshot/text/html
```

## Anti-Patterns

### 1. Feature Creep
Adding tools "just in case" someone needs them.

**Fix**: Only add tools with proven usage patterns.

### 2. Granular Operations
Separate tools for each atomic operation.

**Fix**: Combine related operations with action parameters.

### 3. Inconsistent Naming
`getUser`, `fetch_project`, `listTeams`, `SEARCH_ISSUES`

**Fix**: Consistent `verb_noun` pattern: `get_user`, `list_projects`

### 4. Missing Descriptions
Tools with cryptic names and no description.

**Fix**: Every tool needs clear description + examples.

## Use This Skill When

- Designing new MCP servers
- Auditing existing tool sets
- Improving agent success rates
- Reducing cognitive load on models
- Optimizing Claude Code integrations

## Related Skills

- `api-design-standards` - REST/GraphQL patterns apply to tools
- `llm-project-development` - Pipeline architecture
- `context-management` - Managing context with tools

## Quick Start

```bash
# Audit your tool set
cat checklists/tool-audit-checklist.md

# Learn consolidation patterns
cat reference/consolidation-guide.md

# See real examples
cat examples/mcp-consolidation-examples.md
```

---

**Skill Version**: 1.0
**Key Metric**: 17→2 tools = 80%→100% success
**Last Updated**: 2025-01-15

Files: 5

Size: 24.7 KB

Complexity: 48/100

Category: Design

Source: https://github.com/greyhaven-ai/claude-code-config/tree/main/grey-haven-plugins/core/skills/tool-design

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts