hive-skills 0.1.0

package/assets/skills/converted/mcp-builder/composable/BUNDLE.md

@@ -0,0 +1,2460 @@
+<!-- GENERATED by tools/hive.py compile. Do not hand-edit. -->
+# mcp-builder: Compiled Skill Bundle (v1.0.0)
+
+All composable mini-skills for `mcp-builder` concatenated in index order, frontmatter stripped. Regenerate with `tools/hive.py compile <skill-dir>`. Do not edit by hand.
+
+---
+<!-- module: 00-core.md -->
+
+# Core: MCP Server Quality Mindset
+
+Always-loaded foundation for building high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Load the focused minis (see INDEX) for the workflow, per-standard rules, language-specific code, and evaluations.
+
+## What "quality" means here
+
+Create MCP servers that enable LLMs to interact with external services through well-designed tools. **The quality of an MCP server is measured by how well it enables LLMs to accomplish real-world tasks** — NOT by how well or comprehensively the server implements tools. Quality is about how the implementations (input/output schemas, docstrings/descriptions, functionality) enable an LLM, with no other context and access ONLY to the MCP server, to answer realistic and difficult questions and complete real tasks.
+
+## Agent-first tool design (design for the LLM that will call the tools)
+
+- **API coverage vs. workflow tools:** Balance comprehensive API endpoint coverage with specialized workflow tools. Workflow tools can be more convenient for specific tasks; comprehensive coverage gives agents flexibility to compose operations. Performance varies by client — some clients benefit from code execution that combines basic tools, others work better with higher-level workflows. **When uncertain, prioritize comprehensive API coverage.**
+- **Tool naming and discoverability:** Clear, descriptive tool names help agents find the right tools quickly. Use consistent prefixes (e.g., `github_create_issue`, `github_list_repos`) and action-oriented naming. (Full naming rules: see the naming mini.)
+- **Tools should enable complete workflows, not just wrap API endpoints.** Tool names should reflect natural task subdivisions.
+- **Keep tool operations focused and atomic.**
+
+## Token-consciousness (context is scarce)
+
+- Agents benefit from **concise tool descriptions** and the ability to **filter/paginate** results. Design tools that return **focused, relevant data**.
+- **Response formats should optimize for agent context efficiency.** Omit verbose metadata; return only what the task needs. Some clients support code execution which can help agents filter and process data efficiently.
+- Prefer **human-readable identifiers** where appropriate (display names with IDs, human-readable datetimes) so the agent doesn't waste effort decoding opaque values.
+- Tools that return large JSON objects or lists can overwhelm the LLM — reduce information returned, paginate, and truncate with clear messages.
+
+## Error-message discipline
+
+- **Error messages must guide agents toward solutions** with specific suggestions and next steps — clear, actionable, and educational. An error should tell the agent what to do next (e.g., suggest a filter to reduce results, or the correct alternative tool).
+- Descriptions must **precisely and unambiguously match actual functionality** — never over- or under-claim what a tool does.
+
+## Composability / DRY (applies to every implementation)
+
+Your implementation MUST prioritize composability and code reuse:
+
+1. **Extract common functionality:** reusable helper functions for operations used across multiple tools; shared API clients for HTTP requests; centralized error-handling logic; business logic in dedicated composable functions; shared markdown/JSON field-selection & formatting.
+2. **Avoid duplication:** NEVER copy-paste similar code between tools. If you write similar logic twice, extract it into a function. Common operations (pagination, filtering, field selection, formatting) should be shared. Authentication/authorization logic should be centralized.
+
+## Strategic design checklist (cross-cutting — verify on every server)
+
+- [ ] Tools enable complete workflows, not just API endpoint wrappers
+- [ ] Tool names reflect natural task subdivisions
+- [ ] Response formats optimize for agent context efficiency
+- [ ] Human-readable identifiers used where appropriate
+- [ ] Error messages guide agents toward correct usage
+
+(Language-specific implementation and code-quality checklists live in the Python and Node minis.)
+
+---
+<!-- module: 01-workflow-research-planning.md -->
+
+# Workflow, Research & Planning (Phase 1)
+
+Creating a high-quality MCP server involves **four main phases**: (1) Deep Research and Planning, (2) Implementation, (3) Review and Test, (4) Create Evaluations. This mini covers Phase 1 and how to navigate the reference documentation.
+
+## Phase 1: Deep Research and Planning
+
+### 1.1 Understand modern MCP design
+
+The core design tensions (agent-first design, API coverage vs. workflow tools, naming/discoverability, context management, actionable errors) are covered in `00-core.md`. Internalize those before designing tools.
+
+### 1.2 Study MCP protocol documentation
+
+Navigate the MCP specification:
+- Start with the sitemap to find relevant pages: `https://modelcontextprotocol.io/sitemap.xml`
+- Then fetch specific pages with a `.md` suffix for markdown format (e.g., `https://modelcontextprotocol.io/specification/draft.md`).
+
+Key pages to review:
+- Specification overview and architecture
+- Transport mechanisms (streamable HTTP, stdio)
+- Tool, resource, and prompt definitions
+
+### 1.3 Study framework documentation
+
+**Recommended stack:**
+- **Language: TypeScript** — high-quality SDK support and good compatibility in many execution environments (e.g. MCPB). AI models are good at generating TypeScript code, benefiting from its broad usage, static typing, and good linting tools.
+- **Transport: Streamable HTTP** for remote servers, using **stateless JSON** (simpler to scale and maintain, as opposed to stateful sessions and streaming responses). **stdio** for local servers.
+
+**Load framework documentation:**
+- **MCP Best Practices** — core universal guidelines (see the naming, response-format, pagination, transport, security, annotations, error-handling, and testing minis).
+- **For TypeScript (recommended):** Use WebFetch to load the TypeScript SDK README: `https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md`. Then use the Node/TypeScript implementation minis.
+- **For Python:** Use WebFetch to load the Python SDK README: `https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md`. Then use the Python implementation minis.
+
+### 1.4 Plan your implementation
+
+- **Understand the API:** Review the service's API documentation to identify key endpoints, authentication requirements, and data models. Use web search and WebFetch as needed.
+- **Tool selection:** Prioritize comprehensive API coverage. List the endpoints to implement, starting with the most common operations.
+
+## Documentation library — what to load and when
+
+**Core MCP documentation (load first):**
+- MCP Protocol: start with the sitemap at `https://modelcontextprotocol.io/sitemap.xml`, then fetch specific pages with `.md` suffix.
+- MCP Best Practices — universal guidelines including server/tool naming conventions, response format (JSON vs Markdown), pagination, transport selection (streamable HTTP vs stdio), security, and error handling.
+
+**SDK documentation (load during Phase 1/2):**
+- Python SDK: `https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md`
+- TypeScript SDK: `https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md`
+
+**Language-specific implementation guides (load during Phase 2):**
+- Python (FastMCP): server initialization, Pydantic models, tool registration with `@mcp.tool`, complete working examples, quality checklist.
+- TypeScript: project structure, Zod schema patterns, tool registration with `server.registerTool`, complete working examples, quality checklist.
+
+**Evaluation guide (load during Phase 4):** question creation guidelines, answer verification strategies, XML format, example questions/answers, and running an evaluation with the provided scripts.
+
+The remaining phases: Phase 2 (Implementation) and Phase 3 (Review and Test) — see `02-implementation-process.md`. Phase 4 (Create Evaluations) — see the evaluation minis.
+
+---
+<!-- module: 02-implementation-process.md -->
+
+# Implementation & Review Process (Phases 2–3)
+
+Language-agnostic steps for building and then reviewing/testing the server. Use alongside the language-specific minis (Python or Node) for the actual code.
+
+## Phase 2: Implementation
+
+### 2.1 Set up project structure
+
+See the language-specific minis for project setup:
+- TypeScript: project structure, `package.json`, `tsconfig.json`.
+- Python: module organization, dependencies.
+
+### 2.2 Implement core infrastructure
+
+Create shared utilities:
+- API client with authentication
+- Error handling helpers
+- Response formatting (JSON/Markdown)
+- Pagination support
+
+### 2.3 Implement tools
+
+For each tool:
+
+**Input schema:**
+- Use Zod (TypeScript) or Pydantic (Python)
+- Include constraints and clear descriptions
+- Add examples in field descriptions
+
+**Output schema:**
+- Define `outputSchema` where possible for structured data
+- Use `structuredContent` in tool responses (TypeScript SDK feature)
+- Helps clients understand and process tool outputs
+
+**Tool description:**
+- Concise summary of functionality
+- Parameter descriptions
+- Return type schema
+
+**Implementation:**
+- Async/await for I/O operations
+- Proper error handling with actionable messages
+- Support pagination where applicable
+- Return both text content and structured data when using modern SDKs
+
+**Annotations:**
+- `readOnlyHint`: true/false
+- `destructiveHint`: true/false
+- `idempotentHint`: true/false
+- `openWorldHint`: true/false
+
+(Full annotation semantics: see the annotations mini.)
+
+## Phase 3: Review and Test
+
+### 3.1 Code quality
+
+Review for:
+- No duplicated code (DRY principle)
+- Consistent error handling
+- Full type coverage
+- Clear tool descriptions
+
+### 3.2 Build and test
+
+**TypeScript:**
+- Run `npm run build` to verify compilation
+- Test with MCP Inspector: `npx @modelcontextprotocol/inspector`
+
+**Python:**
+- Verify syntax: `python -m py_compile your_server.py`
+- Test with MCP Inspector
+
+See the language-specific minis for detailed testing approaches and quality checklists.
+
+## Phase 4: Create Evaluations
+
+After implementing your MCP server, create comprehensive evaluations to test its effectiveness. Use evaluations to test whether LLMs can effectively use your MCP server to answer realistic, complex questions. The process (10 questions: tool inspection → content exploration → question generation → answer verification) and the harness for running them are covered in the evaluation minis.
+
+---
+<!-- module: 03-naming-conventions.md -->
+
+# Naming Conventions (Server & Tools)
+
+## Server naming
+
+Follow these standardized naming patterns:
+
+- **Python:** `{service}_mcp` (lowercase with underscores) — e.g., `slack_mcp`, `github_mcp`, `jira_mcp`, `stripe_mcp`.
+- **Node/TypeScript:** `{service}-mcp-server` (lowercase with hyphens) — e.g., `slack-mcp-server`, `github-mcp-server`, `jira-mcp-server`, `stripe-mcp-server`.
+
+The name should be:
+- **General** — descriptive of the service being integrated, not tied to specific features.
+- **Descriptive** of the service/API being integrated.
+- **Easy to infer** from the task description.
+- **Without version numbers** or dates.
+
+## Tool naming
+
+1. **Use snake_case:** `search_users`, `create_project`, `get_channel_info`.
+2. **Include service prefix** — anticipate that your MCP server may be used alongside other MCP servers, so include the service context to prevent overlaps:
+   - Use `slack_send_message` instead of just `send_message`
+   - Use `github_create_issue` instead of just `create_issue`
+   - Use `asana_list_tasks` instead of just `list_tasks`
+3. **Be action-oriented:** start with verbs (get, list, search, create, etc.).
+4. **Be specific:** avoid generic names that could conflict with other servers.
+
+Format: `{service}_{action}_{resource}` — e.g., `slack_send_message`, `github_create_issue`.
+
+## Tool design
+
+- Tool descriptions must **narrowly and unambiguously** describe functionality.
+- Descriptions must **precisely match actual functionality**.
+- Provide tool annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`) — see the annotations mini.
+- Keep tool operations **focused and atomic**.
+
+---
+<!-- module: 04-response-formats.md -->
+
+# Response Formats (JSON vs Markdown)
+
+All tools that return data should support **multiple formats**, typically via a `response_format` parameter that defaults to markdown. JSON is for programmatic processing; Markdown is for human readability.
+
+## JSON format (`response_format="json"`)
+
+- Machine-readable structured data
+- Return complete, structured data suitable for programmatic processing
+- Include all available fields and metadata
+- Use consistent field names and types
+
+## Markdown format (`response_format="markdown"`, typically the default)
+
+- Human-readable formatted text
+- Use headers, lists, and formatting for clarity
+- Convert timestamps to human-readable format (e.g., "2024-01-15 10:30:00 UTC" instead of epoch)
+- Show display names with IDs in parentheses (e.g., "@john.doe (U123456)")
+- Omit verbose metadata (e.g., show only one profile image URL, not all sizes)
+- Group related information logically
+
+(Language-specific code for implementing the `ResponseFormat` enum and formatting both branches lives in the Python and Node minis.)
+
+---
+<!-- module: 05-pagination.md -->
+
+# Pagination
+
+For tools that list resources:
+
+- **Always respect the `limit` parameter.**
+- **Implement pagination:** use `offset` or cursor-based pagination.
+- **Return pagination metadata:** include `has_more`, `next_offset`/`next_cursor`, and `total_count`.
+- **Never load all results into memory** — especially important for large datasets.
+- **Default to reasonable limits:** 20–50 items is typical.
+
+Example pagination response:
+
+```json
+{
+  "total": 150,
+  "count": 20,
+  "offset": 0,
+  "items": [...],
+  "has_more": true,
+  "next_offset": 20
+}
+```
+
+(Language-specific pagination code — computing `has_more` and `next_offset` from `total`, `offset`, and returned items — lives in the Python and Node minis.)
+
+---
+<!-- module: 06-transport.md -->
+
+# Transport Options
+
+Two main transports: **Streamable HTTP** (remote) and **stdio** (local). **Avoid SSE — deprecated in favor of streamable HTTP.**
+
+## Streamable HTTP
+
+**Best for:** remote servers, web services, multi-client scenarios.
+
+**Characteristics:**
+- Bidirectional communication over HTTP
+- Supports multiple simultaneous clients
+- Can be deployed as a web service
+- Enables server-to-client notifications
+
+**Use when:**
+- Serving multiple clients simultaneously
+- Deploying as a cloud service
+- Integrating with web applications
+
+For remote servers, prefer **stateless JSON** (simpler to scale and maintain than stateful sessions and streaming responses).
+
+## stdio
+
+**Best for:** local integrations, command-line tools.
+
+**Characteristics:**
+- Standard input/output stream communication
+- Simple setup, no network configuration needed
+- Runs as a subprocess of the client
+
+**Use when:**
+- Building tools for local development environments
+- Integrating with desktop applications
+- Single-user, single-session scenarios
+
+**Note:** stdio servers must NOT log to stdout — use stderr for logging.
+
+## Transport selection
+
+| Criterion | stdio | Streamable HTTP |
+|-----------|-------|-----------------|
+| **Deployment** | Local | Remote |
+| **Clients** | Single | Multiple |
+| **Complexity** | Low | Medium |
+| **Real-time** | No | Yes |
+
+(Language-specific code for wiring up each transport lives in the Python and Node minis.)
+
+---
+<!-- module: 07-annotations.md -->
+
+# Tool Annotations
+
+Provide annotations to help clients understand tool behavior. Set them on every tool.
+
+| Annotation | Type | Default | Description |
+|-----------|------|---------|-------------|
+| `readOnlyHint` | boolean | false | Tool does not modify its environment |
+| `destructiveHint` | boolean | true | Tool may perform destructive updates |
+| `idempotentHint` | boolean | false | Repeated calls with same args have no additional effect |
+| `openWorldHint` | boolean | true | Tool interacts with external entities |
+
+**Important:** Annotations are **hints, not security guarantees**. Clients should not make security-critical decisions based solely on annotations.
+
+Set each hint to accurately reflect the tool:
+- `readOnlyHint`: true if the tool does not modify environment
+- `destructiveHint`: false if the tool does not perform destructive operations
+- `idempotentHint`: true if repeated calls have no additional effect
+- `openWorldHint`: false if the tool does not interact with external entities
+
+(Language-specific syntax — the `annotations={...}` dict in the `@mcp.tool` decorator for Python, and the `annotations` object in `registerTool` for Node — lives in the language minis.)
+
+---
+<!-- module: 08-security.md -->
+
+# Security Best Practices
+
+## Authentication and Authorization
+
+**OAuth 2.1:**
+- Use secure OAuth 2.1 with certificates from recognized authorities
+- Validate access tokens before processing requests
+- Only accept tokens specifically intended for your server
+
+**API Keys:**
+- Store API keys in environment variables, never in code
+- Validate keys on server startup
+- Provide clear error messages when authentication fails
+
+## Input Validation
+
+- Sanitize file paths to prevent directory traversal
+- Validate URLs and external identifiers
+- Check parameter sizes and ranges
+- Prevent command injection in system calls
+- Use schema validation (Pydantic/Zod) for all inputs
+
+## Error Handling (security angle)
+
+- Don't expose internal errors to clients
+- Log security-relevant errors server-side
+- Provide helpful but not revealing error messages
+- Clean up resources after errors
+
+## DNS Rebinding Protection
+
+For streamable HTTP servers running locally:
+- Enable DNS rebinding protection
+- Validate the `Origin` header on all incoming connections
+- Bind to `127.0.0.1` rather than `0.0.0.0`
+
+---
+<!-- module: 09-error-handling.md -->
+
+# Error Handling Standards
+
+General, cross-language error-handling standards. Language-specific error formatting (`_handle_api_error` in Python, `handleApiError` in Node, mapping 404/403/429/timeout to messages) lives in the language minis.
+
+## Principles
+
+- Use standard **JSON-RPC error codes**.
+- **Report tool errors within result objects** (not protocol-level errors).
+- Provide **helpful, specific error messages with suggested next steps**.
+- **Don't expose internal implementation details.**
+- **Clean up resources properly on errors.**
+
+Error messages should be clear, actionable, and educational — guiding the agent toward a solution with specific suggestions and next steps.
+
+## Example (TypeScript pattern)
+
+```typescript
+try {
+  const result = performOperation();
+  return { content: [{ type: "text", text: result }] };
+} catch (error) {
+  return {
+    isError: true,
+    content: [{
+      type: "text",
+      text: `Error: ${error.message}. Try using filter='active_only' to reduce results.`
+    }]
+  };
+}
+```
+
+Note how the message not only reports the failure but suggests a concrete next step (`filter='active_only'`) that helps the agent recover.
+
+---
+<!-- module: 10-testing-and-documentation.md -->
+
+# Testing & Documentation Requirements
+
+General (language-agnostic) requirements. Language-specific build/test commands and quality checklists live in the Python and Node minis; the evaluation harness is covered in the evaluation minis.
+
+## Testing Requirements
+
+Comprehensive testing should cover:
+
+- **Functional testing:** verify correct execution with valid/invalid inputs.
+- **Integration testing:** test interaction with external systems.
+- **Security testing:** validate auth, input sanitization, rate limiting.
+- **Performance testing:** check behavior under load, timeouts.
+- **Error handling:** ensure proper error reporting and cleanup.
+
+## Documentation Requirements
+
+- Provide clear documentation of all tools and capabilities.
+- Include working examples (**at least 3 per major feature**).
+- Document security considerations.
+- Specify required permissions and access levels.
+- Document rate limits and performance characteristics.
+
+---
+<!-- module: 11-python-implementation.md -->
+
+# Python (FastMCP) — Implementation Patterns
+
+Python-specific best practices and code for implementing MCP servers with the MCP Python SDK (FastMCP): server setup, tool registration, input validation with Pydantic, error handling, and a complete working example. Server naming (`{service}_mcp`) and tool naming are in the naming mini; this mini is the how-in-Python.
+
+## MCP Python SDK and FastMCP
+
+The official MCP Python SDK provides FastMCP, a high-level framework for building MCP servers. It provides:
+- Automatic description and inputSchema generation from function signatures and docstrings
+- Pydantic model integration for input validation
+- Decorator-based tool registration with `@mcp.tool`
+
+For complete SDK documentation, use WebFetch to load: `https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md`
+
+## Quick Reference
+
+### Key imports
+```python
+from mcp.server.fastmcp import FastMCP
+from pydantic import BaseModel, Field, field_validator, ConfigDict
+from typing import Optional, List, Dict, Any
+from enum import Enum
+import httpx
+```
+
+### Server initialization
+```python
+mcp = FastMCP("service_mcp")
+```
+
+### Tool registration pattern
+```python
+@mcp.tool(name="tool_name", annotations={...})
+async def tool_function(params: InputModel) -> str:
+    # Implementation
+    pass
+```
+
+## Tool Structure with FastMCP
+
+Tools are defined using the `@mcp.tool` decorator with Pydantic models for input validation. Use snake_case, action-oriented tool names with a service prefix (e.g., `slack_send_message`, `github_create_issue`, `asana_list_tasks`).
+
+```python
+from pydantic import BaseModel, Field, ConfigDict
+from mcp.server.fastmcp import FastMCP
+
+# Initialize the MCP server
+mcp = FastMCP("example_mcp")
+
+# Define Pydantic model for input validation
+class ServiceToolInput(BaseModel):
+    '''Input model for service tool operation.'''
+    model_config = ConfigDict(
+        str_strip_whitespace=True,  # Auto-strip whitespace from strings
+        validate_assignment=True,    # Validate on assignment
+        extra='forbid'              # Forbid extra fields
+    )
+
+    param1: str = Field(..., description="First parameter description (e.g., 'user123', 'project-abc')", min_length=1, max_length=100)
+    param2: Optional[int] = Field(default=None, description="Optional integer parameter with constraints", ge=0, le=1000)
+    tags: Optional[List[str]] = Field(default_factory=list, description="List of tags to apply", max_items=10)
+
+@mcp.tool(
+    name="service_tool_name",
+    annotations={
+        "title": "Human-Readable Tool Title",
+        "readOnlyHint": True,     # Tool does not modify environment
+        "destructiveHint": False,  # Tool does not perform destructive operations
+        "idempotentHint": True,    # Repeated calls have no additional effect
+        "openWorldHint": False     # Tool does not interact with external entities
+    }
+)
+async def service_tool_name(params: ServiceToolInput) -> str:
+    '''Tool description automatically becomes the 'description' field.
+
+    This tool performs a specific operation on the service. It validates all inputs
+    using the ServiceToolInput Pydantic model before processing.
+
+    Args:
+        params (ServiceToolInput): Validated input parameters containing:
+            - param1 (str): First parameter description
+            - param2 (Optional[int]): Optional parameter with default
+            - tags (Optional[List[str]]): List of tags
+
+    Returns:
+        str: JSON-formatted response containing operation results
+    '''
+    # Implementation here
+    pass
+```
+
+## Pydantic v2 Key Features
+
+- Use `model_config` instead of nested `Config` class
+- Use `field_validator` instead of deprecated `validator`
+- Use `model_dump()` instead of deprecated `dict()`
+- Validators require `@classmethod` decorator
+- Type hints are required for validator methods
+
+```python
+from pydantic import BaseModel, Field, field_validator, ConfigDict
+
+class CreateUserInput(BaseModel):
+    model_config = ConfigDict(
+        str_strip_whitespace=True,
+        validate_assignment=True
+    )
+
+    name: str = Field(..., description="User's full name", min_length=1, max_length=100)
+    email: str = Field(..., description="User's email address", pattern=r'^[\w\.-]+@[\w\.-]+\.\w+$')
+    age: int = Field(..., description="User's age", ge=0, le=150)
+
+    @field_validator('email')
+    @classmethod
+    def validate_email(cls, v: str) -> str:
+        if not v.strip():
+            raise ValueError("Email cannot be empty")
+        return v.lower()
+```
+
+## Response Format Options
+
+Support multiple output formats for flexibility (concept in the response-formats mini):
+
+```python
+from enum import Enum
+
+class ResponseFormat(str, Enum):
+    '''Output format for tool responses.'''
+    MARKDOWN = "markdown"
+    JSON = "json"
+
+class UserSearchInput(BaseModel):
+    query: str = Field(..., description="Search query")
+    response_format: ResponseFormat = Field(
+        default=ResponseFormat.MARKDOWN,
+        description="Output format: 'markdown' for human-readable or 'json' for machine-readable"
+    )
+```
+
+**Markdown format:** use headers, lists, and formatting for clarity; convert timestamps to human-readable format (e.g., "2024-01-15 10:30:00 UTC" instead of epoch); show display names with IDs in parentheses (e.g., "@john.doe (U123456)"); omit verbose metadata (e.g., show only one profile image URL, not all sizes); group related information logically.
+
+**JSON format:** return complete, structured data suitable for programmatic processing; include all available fields and metadata; use consistent field names and types.
+
+## Pagination Implementation
+
+```python
+class ListInput(BaseModel):
+    limit: Optional[int] = Field(default=20, description="Maximum results to return", ge=1, le=100)
+    offset: Optional[int] = Field(default=0, description="Number of results to skip for pagination", ge=0)
+
+async def list_items(params: ListInput) -> str:
+    # Make API request with pagination
+    data = await api_request(limit=params.limit, offset=params.offset)
+
+    # Return pagination info
+    response = {
+        "total": data["total"],
+        "count": len(data["items"]),
+        "offset": params.offset,
+        "items": data["items"],
+        "has_more": data["total"] > params.offset + len(data["items"]),
+        "next_offset": params.offset + len(data["items"]) if data["total"] > params.offset + len(data["items"]) else None
+    }
+    return json.dumps(response, indent=2)
+```
+
+## Error Handling
+
+Provide clear, actionable error messages:
+
+```python
+def _handle_api_error(e: Exception) -> str:
+    '''Consistent error formatting across all tools.'''
+    if isinstance(e, httpx.HTTPStatusError):
+        if e.response.status_code == 404:
+            return "Error: Resource not found. Please check the ID is correct."
+        elif e.response.status_code == 403:
+            return "Error: Permission denied. You don't have access to this resource."
+        elif e.response.status_code == 429:
+            return "Error: Rate limit exceeded. Please wait before making more requests."
+        return f"Error: API request failed with status {e.response.status_code}"
+    elif isinstance(e, httpx.TimeoutException):
+        return "Error: Request timed out. Please try again."
+    return f"Error: Unexpected error occurred: {type(e).__name__}"
+```
+
+## Shared Utilities
+
+Extract common functionality into reusable functions:
+
+```python
+# Shared API request function
+async def _make_api_request(endpoint: str, method: str = "GET", **kwargs) -> dict:
+    '''Reusable function for all API calls.'''
+    async with httpx.AsyncClient() as client:
+        response = await client.request(
+            method,
+            f"{API_BASE_URL}/{endpoint}",
+            timeout=30.0,
+            **kwargs
+        )
+        response.raise_for_status()
+        return response.json()
+```
+
+## Async/Await Best Practices
+
+Always use async/await for network requests and I/O operations:
+
+```python
+# Good: Async network request
+async def fetch_data(resource_id: str) -> dict:
+    async with httpx.AsyncClient() as client:
+        response = await client.get(f"{API_URL}/resource/{resource_id}")
+        response.raise_for_status()
+        return response.json()
+
+# Bad: Synchronous request
+def fetch_data(resource_id: str) -> dict:
+    response = requests.get(f"{API_URL}/resource/{resource_id}")  # Blocks
+    return response.json()
+```
+
+## Type Hints
+
+Use type hints throughout:
+
+```python
+from typing import Optional, List, Dict, Any
+
+async def get_user(user_id: str) -> Dict[str, Any]:
+    data = await fetch_user(user_id)
+    return {"id": data["id"], "name": data["name"]}
+```
+
+## Tool Docstrings
+
+Every tool must have comprehensive docstrings with explicit type information, including the complete schema structure for dict/JSON returns and usage examples:
+
+```python
+async def search_users(params: UserSearchInput) -> str:
+    '''
+    Search for users in the Example system by name, email, or team.
+
+    This tool searches across all user profiles in the Example platform,
+    supporting partial matches and various search filters. It does NOT
+    create or modify users, only searches existing ones.
+
+    Args:
+        params (UserSearchInput): Validated input parameters containing:
+            - query (str): Search string to match against names/emails (e.g., "john", "@example.com", "team:marketing")
+            - limit (Optional[int]): Maximum results to return, between 1-100 (default: 20)
+            - offset (Optional[int]): Number of results to skip for pagination (default: 0)
+
+    Returns:
+        str: JSON-formatted string containing search results with the following schema:
+
+        Success response:
+        {
+            "total": int,           # Total number of matches found
+            "count": int,           # Number of results in this response
+            "offset": int,          # Current pagination offset
+            "users": [
+                {
+                    "id": str,      # User ID (e.g., "U123456789")
+                    "name": str,    # Full name (e.g., "John Doe")
+                    "email": str,   # Email address (e.g., "john@example.com")
+                    "team": str     # Team name (e.g., "Marketing") - optional
+                }
+            ]
+        }
+
+        Error response:
+        "Error: <error message>" or "No users found matching '<query>'"
+
+    Examples:
+        - Use when: "Find all marketing team members" -> params with query="team:marketing"
+        - Use when: "Search for John's account" -> params with query="john"
+        - Don't use when: You need to create a user (use example_create_user instead)
+        - Don't use when: You have a user ID and need full details (use example_get_user instead)
+
+    Error Handling:
+        - Input validation errors are handled by Pydantic model
+        - Returns "Error: Rate limit exceeded" if too many requests (429 status)
+        - Returns "Error: Invalid API authentication" if API key is invalid (401 status)
+        - Returns formatted list of results or "No users found matching 'query'"
+    '''
+```
+
+## Complete Example
+
+```python
+#!/usr/bin/env python3
+'''
+MCP Server for Example Service.
+
+This server provides tools to interact with Example API, including user search,
+project management, and data export capabilities.
+'''
+
+from typing import Optional, List, Dict, Any
+from enum import Enum
+import httpx
+from pydantic import BaseModel, Field, field_validator, ConfigDict
+from mcp.server.fastmcp import FastMCP
+
+# Initialize the MCP server
+mcp = FastMCP("example_mcp")
+
+# Constants
+API_BASE_URL = "https://api.example.com/v1"
+
+# Enums
+class ResponseFormat(str, Enum):
+    '''Output format for tool responses.'''
+    MARKDOWN = "markdown"
+    JSON = "json"
+
+# Pydantic Models for Input Validation
+class UserSearchInput(BaseModel):
+    '''Input model for user search operations.'''
+    model_config = ConfigDict(
+        str_strip_whitespace=True,
+        validate_assignment=True
+    )
+
+    query: str = Field(..., description="Search string to match against names/emails", min_length=2, max_length=200)
+    limit: Optional[int] = Field(default=20, description="Maximum results to return", ge=1, le=100)
+    offset: Optional[int] = Field(default=0, description="Number of results to skip for pagination", ge=0)
+    response_format: ResponseFormat = Field(default=ResponseFormat.MARKDOWN, description="Output format")
+
+    @field_validator('query')
+    @classmethod
+    def validate_query(cls, v: str) -> str:
+        if not v.strip():
+            raise ValueError("Query cannot be empty or whitespace only")
+        return v.strip()
+
+# Shared utility functions
+async def _make_api_request(endpoint: str, method: str = "GET", **kwargs) -> dict:
+    '''Reusable function for all API calls.'''
+    async with httpx.AsyncClient() as client:
+        response = await client.request(
+            method,
+            f"{API_BASE_URL}/{endpoint}",
+            timeout=30.0,
+            **kwargs
+        )
+        response.raise_for_status()
+        return response.json()
+
+def _handle_api_error(e: Exception) -> str:
+    '''Consistent error formatting across all tools.'''
+    if isinstance(e, httpx.HTTPStatusError):
+        if e.response.status_code == 404:
+            return "Error: Resource not found. Please check the ID is correct."
+        elif e.response.status_code == 403:
+            return "Error: Permission denied. You don't have access to this resource."
+        elif e.response.status_code == 429:
+            return "Error: Rate limit exceeded. Please wait before making more requests."
+        return f"Error: API request failed with status {e.response.status_code}"
+    elif isinstance(e, httpx.TimeoutException):
+        return "Error: Request timed out. Please try again."
+    return f"Error: Unexpected error occurred: {type(e).__name__}"
+
+# Tool definitions
+@mcp.tool(
+    name="example_search_users",
+    annotations={
+        "title": "Search Example Users",
+        "readOnlyHint": True,
+        "destructiveHint": False,
+        "idempotentHint": True,
+        "openWorldHint": True
+    }
+)
+async def example_search_users(params: UserSearchInput) -> str:
+    '''Search for users in the Example system by name, email, or team.
+
+    [Full docstring as shown above]
+    '''
+    try:
+        # Make API request using validated parameters
+        data = await _make_api_request(
+            "users/search",
+            params={
+                "q": params.query,
+                "limit": params.limit,
+                "offset": params.offset
+            }
+        )
+
+        users = data.get("users", [])
+        total = data.get("total", 0)
+
+        if not users:
+            return f"No users found matching '{params.query}'"
+
+        # Format response based on requested format
+        if params.response_format == ResponseFormat.MARKDOWN:
+            lines = [f"# User Search Results: '{params.query}'", ""]
+            lines.append(f"Found {total} users (showing {len(users)})")
+            lines.append("")
+
+            for user in users:
+                lines.append(f"## {user['name']} ({user['id']})")
+                lines.append(f"- **Email**: {user['email']}")
+                if user.get('team'):
+                    lines.append(f"- **Team**: {user['team']}")
+                lines.append("")
+
+            return "\n".join(lines)
+
+        else:
+            # Machine-readable JSON format
+            import json
+            response = {
+                "total": total,
+                "count": len(users),
+                "offset": params.offset,
+                "users": users
+            }
+            return json.dumps(response, indent=2)
+
+    except Exception as e:
+        return _handle_api_error(e)
+
+if __name__ == "__main__":
+    mcp.run()
+```
+
+Advanced FastMCP features (context injection, resources, structured output, lifespan, transport), Python-specific best practices, and the quality checklist are in `12-python-advanced-and-checklist.md`.
+
+---
+<!-- module: 12-python-advanced-and-checklist.md -->
+
+# Python (FastMCP) — Advanced Features & Quality Checklist
+
+Continues `11-python-implementation.md`. Advanced FastMCP capabilities, Python-specific best practices, and the finalization checklist.
+
+## Advanced FastMCP Features
+
+### Context Parameter Injection
+
+FastMCP can automatically inject a `Context` parameter into tools for advanced capabilities like logging, progress reporting, resource reading, and user interaction:
+
+```python
+from mcp.server.fastmcp import FastMCP, Context
+
+mcp = FastMCP("example_mcp")
+
+@mcp.tool()
+async def advanced_search(query: str, ctx: Context) -> str:
+    '''Advanced tool with context access for logging and progress.'''
+
+    # Report progress for long operations
+    await ctx.report_progress(0.25, "Starting search...")
+
+    # Log information for debugging
+    await ctx.log_info("Processing query", {"query": query, "timestamp": datetime.now()})
+
+    # Perform search
+    results = await search_api(query)
+    await ctx.report_progress(0.75, "Formatting results...")
+
+    # Access server configuration
+    server_name = ctx.fastmcp.name
+
+    return format_results(results)
+
+@mcp.tool()
+async def interactive_tool(resource_id: str, ctx: Context) -> str:
+    '''Tool that can request additional input from users.'''
+
+    # Request sensitive information when needed
+    api_key = await ctx.elicit(
+        prompt="Please provide your API key:",
+        input_type="password"
+    )
+
+    # Use the provided key
+    return await api_call(resource_id, api_key)
+```
+
+**Context capabilities:**
+- `ctx.report_progress(progress, message)` — Report progress for long operations
+- `ctx.log_info(message, data)` / `ctx.log_error()` / `ctx.log_debug()` — Logging
+- `ctx.elicit(prompt, input_type)` — Request input from users
+- `ctx.fastmcp.name` — Access server configuration
+- `ctx.read_resource(uri)` — Read MCP resources
+
+### Resource Registration
+
+Expose data as resources for efficient, template-based access:
+
+```python
+@mcp.resource("file://documents/{name}")
+async def get_document(name: str) -> str:
+    '''Expose documents as MCP resources.
+
+    Resources are useful for static or semi-static data that doesn't
+    require complex parameters. They use URI templates for flexible access.
+    '''
+    document_path = f"./docs/{name}"
+    with open(document_path, "r") as f:
+        return f.read()
+
+@mcp.resource("config://settings/{key}")
+async def get_setting(key: str, ctx: Context) -> str:
+    '''Expose configuration as resources with context.'''
+    settings = await load_settings()
+    return json.dumps(settings.get(key, {}))
+```
+
+**When to use Resources vs Tools:**
+- **Resources:** for data access with simple parameters (URI templates)
+- **Tools:** for complex operations with validation and business logic
+
+### Structured Output Types
+
+FastMCP supports multiple return types beyond strings:
+
+```python
+from typing import TypedDict
+from dataclasses import dataclass
+from pydantic import BaseModel
+
+# TypedDict for structured returns
+class UserData(TypedDict):
+    id: str
+    name: str
+    email: str
+
+@mcp.tool()
+async def get_user_typed(user_id: str) -> UserData:
+    '''Returns structured data - FastMCP handles serialization.'''
+    return {"id": user_id, "name": "John Doe", "email": "john@example.com"}
+
+# Pydantic models for complex validation
+class DetailedUser(BaseModel):
+    id: str
+    name: str
+    email: str
+    created_at: datetime
+    metadata: Dict[str, Any]
+
+@mcp.tool()
+async def get_user_detailed(user_id: str) -> DetailedUser:
+    '''Returns Pydantic model - automatically generates schema.'''
+    user = await fetch_user(user_id)
+    return DetailedUser(**user)
+```
+
+### Lifespan Management
+
+Initialize resources that persist across requests:
+
+```python
+from contextlib import asynccontextmanager
+
+@asynccontextmanager
+async def app_lifespan():
+    '''Manage resources that live for the server's lifetime.'''
+    # Initialize connections, load config, etc.
+    db = await connect_to_database()
+    config = load_configuration()
+
+    # Make available to all tools
+    yield {"db": db, "config": config}
+
+    # Cleanup on shutdown
+    await db.close()
+
+mcp = FastMCP("example_mcp", lifespan=app_lifespan)
+
+@mcp.tool()
+async def query_data(query: str, ctx: Context) -> str:
+    '''Access lifespan resources through context.'''
+    db = ctx.request_context.lifespan_state["db"]
+    results = await db.query(query)
+    return format_results(results)
+```
+
+### Transport Options
+
+FastMCP supports two main transport mechanisms:
+
+```python
+# stdio transport (for local tools) - default
+if __name__ == "__main__":
+    mcp.run()
+
+# Streamable HTTP transport (for remote servers)
+if __name__ == "__main__":
+    mcp.run(transport="streamable_http", port=8000)
+```
+
+**Transport selection:**
+- **stdio:** command-line tools, local integrations, subprocess execution
+- **Streamable HTTP:** web services, remote access, multiple clients
+
+## Code Best Practices
+
+### Code Composability and Reusability
+
+Prioritize composability and code reuse (the general rule is in `00-core.md`): extract common functionality into reusable helper functions, shared API clients, centralized error handling, composable business logic, and shared markdown/JSON field-selection & formatting. NEVER copy-paste similar code between tools; if you write similar logic twice, extract it. Share pagination, filtering, field selection, and formatting; centralize authentication/authorization.
+
+### Python-Specific Best Practices
+
+1. **Use Type Hints:** always include type annotations for function parameters and return values.
+2. **Pydantic Models:** define clear Pydantic models for all input validation.
+3. **Avoid Manual Validation:** let Pydantic handle input validation with constraints.
+4. **Proper Imports:** group imports (standard library, third-party, local).
+5. **Error Handling:** use specific exception types (`httpx.HTTPStatusError`, not generic `Exception`).
+6. **Async Context Managers:** use `async with` for resources that need cleanup.
+7. **Constants:** define module-level constants in UPPER_CASE.
+
+## Quality Checklist
+
+Before finalizing your Python MCP server implementation, ensure:
+
+### Strategic Design
+- [ ] Tools enable complete workflows, not just API endpoint wrappers
+- [ ] Tool names reflect natural task subdivisions
+- [ ] Response formats optimize for agent context efficiency
+- [ ] Human-readable identifiers used where appropriate
+- [ ] Error messages guide agents toward correct usage
+
+### Implementation Quality
+- [ ] FOCUSED IMPLEMENTATION: Most important and valuable tools implemented
+- [ ] All tools have descriptive names and documentation
+- [ ] Return types are consistent across similar operations
+- [ ] Error handling is implemented for all external calls
+- [ ] Server name follows format: `{service}_mcp`
+- [ ] All network operations use async/await
+- [ ] Common functionality is extracted into reusable functions
+- [ ] Error messages are clear, actionable, and educational
+- [ ] Outputs are properly validated and formatted
+
+### Tool Configuration
+- [ ] All tools implement 'name' and 'annotations' in the decorator
+- [ ] Annotations correctly set (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
+- [ ] All tools use Pydantic BaseModel for input validation with Field() definitions
+- [ ] All Pydantic Fields have explicit types and descriptions with constraints
+- [ ] All tools have comprehensive docstrings with explicit input/output types
+- [ ] Docstrings include complete schema structure for dict/JSON returns
+- [ ] Pydantic models handle input validation (no manual validation needed)
+
+### Advanced Features (where applicable)
+- [ ] Context injection used for logging, progress, or elicitation
+- [ ] Resources registered for appropriate data endpoints
+- [ ] Lifespan management implemented for persistent connections
+- [ ] Structured output types used (TypedDict, Pydantic models)
+- [ ] Appropriate transport configured (stdio or streamable HTTP)
+
+### Code Quality
+- [ ] File includes proper imports including Pydantic imports
+- [ ] Pagination is properly implemented where applicable
+- [ ] Filtering options are provided for potentially large result sets
+- [ ] All async functions are properly defined with `async def`
+- [ ] HTTP client usage follows async patterns with proper context managers
+- [ ] Type hints are used throughout the code
+- [ ] Constants are defined at module level in UPPER_CASE
+
+### Testing
+- [ ] Server runs successfully: `python your_server.py --help`
+- [ ] All imports resolve correctly
+- [ ] Sample tool calls work as expected
+- [ ] Error scenarios handled gracefully
+
+---
+<!-- module: 13-node-implementation.md -->
+
+# Node/TypeScript — Implementation Patterns
+
+Node/TypeScript-specific best practices and code for implementing MCP servers with the MCP TypeScript SDK: project structure, server setup, tool registration, input validation with Zod, error handling, and a complete working example. Server naming (`{service}-mcp-server`) and tool naming are in the naming mini; this mini is the how-in-TypeScript.
+
+## MCP TypeScript SDK
+
+The official MCP TypeScript SDK provides:
+- `McpServer` class for server initialization
+- `registerTool` method for tool registration
+- Zod schema integration for runtime input validation
+- Type-safe tool handler implementations
+
+**IMPORTANT — Use Modern APIs Only:**
+- **DO use:** `server.registerTool()`, `server.registerResource()`, `server.registerPrompt()`
+- **DO NOT use:** old deprecated APIs such as `server.tool()`, `server.setRequestHandler(ListToolsRequestSchema, ...)`, or manual handler registration.
+- The `register*` methods provide better type safety, automatic schema handling, and are the recommended approach.
+
+For complete SDK details use WebFetch: `https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md`
+
+## Quick Reference
+
+### Key imports
+```typescript
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { StreamableHTTPServerTransport } from "@modelcontextprotocol/sdk/server/streamableHttp.js";
+import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
+import express from "express";
+import { z } from "zod";
+```
+
+### Server initialization
+```typescript
+const server = new McpServer({
+  name: "service-mcp-server",
+  version: "1.0.0"
+});
+```
+
+### Tool registration pattern
+```typescript
+server.registerTool(
+  "tool_name",
+  {
+    title: "Tool Display Name",
+    description: "What the tool does",
+    inputSchema: { param: z.string() },
+    outputSchema: { result: z.string() }
+  },
+  async ({ param }) => {
+    const output = { result: `Processed: ${param}` };
+    return {
+      content: [{ type: "text", text: JSON.stringify(output) }],
+      structuredContent: output // Modern pattern for structured data
+    };
+  }
+);
+```
+
+## Project Structure
+
+```
+{service}-mcp-server/
+├── package.json
+├── tsconfig.json
+├── README.md
+├── src/
+│   ├── index.ts          # Main entry point with McpServer initialization
+│   ├── types.ts          # TypeScript type definitions and interfaces
+│   ├── tools/            # Tool implementations (one file per domain)
+│   ├── services/         # API clients and shared utilities
+│   ├── schemas/          # Zod validation schemas
+│   └── constants.ts      # Shared constants (API_URL, CHARACTER_LIMIT, etc.)
+└── dist/                 # Built JavaScript files (entry point: dist/index.js)
+```
+
+## Tool Structure
+
+Use snake_case, action-oriented tool names with a service prefix (e.g., `slack_send_message`, `github_create_issue`, `asana_list_tasks`). Tools are registered using `registerTool`:
+- Use Zod schemas for runtime input validation and type safety.
+- The `description` field must be explicitly provided — JSDoc comments are NOT automatically extracted.
+- Explicitly provide `title`, `description`, `inputSchema`, and `annotations`.
+- The `inputSchema` must be a Zod schema object (not a JSON schema).
+- Type all parameters and return values explicitly.
+
+```typescript
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { z } from "zod";
+
+const server = new McpServer({
+  name: "example-mcp",
+  version: "1.0.0"
+});
+
+// Zod schema for input validation
+const UserSearchInputSchema = z.object({
+  query: z.string()
+    .min(2, "Query must be at least 2 characters")
+    .max(200, "Query must not exceed 200 characters")
+    .describe("Search string to match against names/emails"),
+  limit: z.number()
+    .int()
+    .min(1)
+    .max(100)
+    .default(20)
+    .describe("Maximum results to return"),
+  offset: z.number()
+    .int()
+    .min(0)
+    .default(0)
+    .describe("Number of results to skip for pagination"),
+  response_format: z.nativeEnum(ResponseFormat)
+    .default(ResponseFormat.MARKDOWN)
+    .describe("Output format: 'markdown' for human-readable or 'json' for machine-readable")
+}).strict();
+
+// Type definition from Zod schema
+type UserSearchInput = z.infer<typeof UserSearchInputSchema>;
+
+server.registerTool(
+  "example_search_users",
+  {
+    title: "Search Example Users",
+    description: `Search for users in the Example system by name, email, or team.
+
+This tool searches across all user profiles in the Example platform, supporting partial matches and various search filters. It does NOT create or modify users, only searches existing ones.
+
+Args:
+  - query (string): Search string to match against names/emails
+  - limit (number): Maximum results to return, between 1-100 (default: 20)
+  - offset (number): Number of results to skip for pagination (default: 0)
+  - response_format ('markdown' | 'json'): Output format (default: 'markdown')
+
+Returns:
+  For JSON format: Structured data with schema:
+  {
+    "total": number,           // Total number of matches found
+    "count": number,           // Number of results in this response
+    "offset": number,          // Current pagination offset
+    "users": [
+      {
+        "id": string,          // User ID (e.g., "U123456789")
+        "name": string,        // Full name (e.g., "John Doe")
+        "email": string,       // Email address
+        "team": string,        // Team name (optional)
+        "active": boolean      // Whether user is active
+      }
+    ],
+    "has_more": boolean,       // Whether more results are available
+    "next_offset": number      // Offset for next page (if has_more is true)
+  }
+
+Examples:
+  - Use when: "Find all marketing team members" -> params with query="team:marketing"
+  - Use when: "Search for John's account" -> params with query="john"
+  - Don't use when: You need to create a user (use example_create_user instead)
+
+Error Handling:
+  - Returns "Error: Rate limit exceeded" if too many requests (429 status)
+  - Returns "No users found matching '<query>'" if search returns empty`,
+    inputSchema: UserSearchInputSchema,
+    annotations: {
+      readOnlyHint: true,
+      destructiveHint: false,
+      idempotentHint: true,
+      openWorldHint: true
+    }
+  },
+  async (params: UserSearchInput) => {
+    try {
+      // Input validation is handled by Zod schema
+      // Make API request using validated parameters
+      const data = await makeApiRequest<any>(
+        "users/search",
+        "GET",
+        undefined,
+        {
+          q: params.query,
+          limit: params.limit,
+          offset: params.offset
+        }
+      );
+
+      const users = data.users || [];
+      const total = data.total || 0;
+
+      if (!users.length) {
+        return {
+          content: [{
+            type: "text",
+            text: `No users found matching '${params.query}'`
+          }]
+        };
+      }
+
+      // Prepare structured output
+      const output = {
+        total,
+        count: users.length,
+        offset: params.offset,
+        users: users.map((user: any) => ({
+          id: user.id,
+          name: user.name,
+          email: user.email,
+          ...(user.team ? { team: user.team } : {}),
+          active: user.active ?? true
+        })),
+        has_more: total > params.offset + users.length,
+        ...(total > params.offset + users.length ? {
+          next_offset: params.offset + users.length
+        } : {})
+      };
+
+      // Format text representation based on requested format
+      let textContent: string;
+      if (params.response_format === ResponseFormat.MARKDOWN) {
+        const lines = [`# User Search Results: '${params.query}'`, "",
+          `Found ${total} users (showing ${users.length})`, ""];
+        for (const user of users) {
+          lines.push(`## ${user.name} (${user.id})`);
+          lines.push(`- **Email**: ${user.email}`);
+          if (user.team) lines.push(`- **Team**: ${user.team}`);
+          lines.push("");
+        }
+        textContent = lines.join("\n");
+      } else {
+        textContent = JSON.stringify(output, null, 2);
+      }
+
+      return {
+        content: [{ type: "text", text: textContent }],
+        structuredContent: output // Modern pattern for structured data
+      };
+    } catch (error) {
+      return {
+        content: [{
+          type: "text",
+          text: handleApiError(error)
+        }]
+      };
+    }
+  }
+);
+```
+
+## Zod Schemas for Input Validation
+
+Zod provides runtime type validation:
+
+```typescript
+import { z } from "zod";
+
+// Basic schema with validation
+const CreateUserSchema = z.object({
+  name: z.string()
+    .min(1, "Name is required")
+    .max(100, "Name must not exceed 100 characters"),
+  email: z.string()
+    .email("Invalid email format"),
+  age: z.number()
+    .int("Age must be a whole number")
+    .min(0, "Age cannot be negative")
+    .max(150, "Age cannot be greater than 150")
+}).strict();  // Use .strict() to forbid extra fields
+
+// Enums
+enum ResponseFormat {
+  MARKDOWN = "markdown",
+  JSON = "json"
+}
+
+const SearchSchema = z.object({
+  response_format: z.nativeEnum(ResponseFormat)
+    .default(ResponseFormat.MARKDOWN)
+    .describe("Output format")
+});
+
+// Optional fields with defaults
+const PaginationSchema = z.object({
+  limit: z.number()
+    .int()
+    .min(1)
+    .max(100)
+    .default(20)
+    .describe("Maximum results to return"),
+  offset: z.number()
+    .int()
+    .min(0)
+    .default(0)
+    .describe("Number of results to skip")
+});
+```
+
+## Response Format Options
+
+Support multiple output formats for flexibility (concept in the response-formats mini):
+
+```typescript
+enum ResponseFormat {
+  MARKDOWN = "markdown",
+  JSON = "json"
+}
+
+const inputSchema = z.object({
+  query: z.string(),
+  response_format: z.nativeEnum(ResponseFormat)
+    .default(ResponseFormat.MARKDOWN)
+    .describe("Output format: 'markdown' for human-readable or 'json' for machine-readable")
+});
+```
+
+**Markdown format:** use headers, lists, and formatting for clarity; convert timestamps to human-readable format; show display names with IDs in parentheses; omit verbose metadata; group related information logically.
+
+**JSON format:** return complete, structured data suitable for programmatic processing; include all available fields and metadata; use consistent field names and types.
+
+## Pagination Implementation
+
+```typescript
+const ListSchema = z.object({
+  limit: z.number().int().min(1).max(100).default(20),
+  offset: z.number().int().min(0).default(0)
+});
+
+async function listItems(params: z.infer<typeof ListSchema>) {
+  const data = await apiRequest(params.limit, params.offset);
+
+  const response = {
+    total: data.total,
+    count: data.items.length,
+    offset: params.offset,
+    items: data.items,
+    has_more: data.total > params.offset + data.items.length,
+    next_offset: data.total > params.offset + data.items.length
+      ? params.offset + data.items.length
+      : undefined
+  };
+
+  return JSON.stringify(response, null, 2);
+}
+```
+
+## Character Limits and Truncation
+
+Add a CHARACTER_LIMIT constant to prevent overwhelming responses:
+
+```typescript
+// At module level in constants.ts
+export const CHARACTER_LIMIT = 25000;  // Maximum response size in characters
+
+async function searchTool(params: SearchInput) {
+  let result = generateResponse(data);
+
+  // Check character limit and truncate if needed
+  if (result.length > CHARACTER_LIMIT) {
+    const truncatedData = data.slice(0, Math.max(1, data.length / 2));
+    response.data = truncatedData;
+    response.truncated = true;
+    response.truncation_message =
+      `Response truncated from ${data.length} to ${truncatedData.length} items. ` +
+      `Use 'offset' parameter or add filters to see more results.`;
+    result = JSON.stringify(response, null, 2);
+  }
+
+  return result;
+}
+```
+
+## Error Handling
+
+Provide clear, actionable error messages:
+
+```typescript
+import axios, { AxiosError } from "axios";
+
+function handleApiError(error: unknown): string {
+  if (error instanceof AxiosError) {
+    if (error.response) {
+      switch (error.response.status) {
+        case 404:
+          return "Error: Resource not found. Please check the ID is correct.";
+        case 403:
+          return "Error: Permission denied. You don't have access to this resource.";
+        case 429:
+          return "Error: Rate limit exceeded. Please wait before making more requests.";
+        default:
+          return `Error: API request failed with status ${error.response.status}`;
+      }
+    } else if (error.code === "ECONNABORTED") {
+      return "Error: Request timed out. Please try again.";
+    }
+  }
+  return `Error: Unexpected error occurred: ${error instanceof Error ? error.message : String(error)}`;
+}
+```
+
+## Shared Utilities
+
+Extract common functionality into reusable functions:
+
+```typescript
+// Shared API request function
+async function makeApiRequest<T>(
+  endpoint: string,
+  method: "GET" | "POST" | "PUT" | "DELETE" = "GET",
+  data?: any,
+  params?: any
+): Promise<T> {
+  try {
+    const response = await axios({
+      method,
+      url: `${API_BASE_URL}/${endpoint}`,
+      data,
+      params,
+      timeout: 30000,
+      headers: {
+        "Content-Type": "application/json",
+        "Accept": "application/json"
+      }
+    });
+    return response.data;
+  } catch (error) {
+    throw error;
+  }
+}
+```
+
+## Async/Await Best Practices
+
+Always use async/await for network requests and I/O operations:
+
+```typescript
+// Good: Async network request
+async function fetchData(resourceId: string): Promise<ResourceData> {
+  const response = await axios.get(`${API_URL}/resource/${resourceId}`);
+  return response.data;
+}
+
+// Bad: Promise chains
+function fetchData(resourceId: string): Promise<ResourceData> {
+  return axios.get(`${API_URL}/resource/${resourceId}`)
+    .then(response => response.data);  // Harder to read and maintain
+}
+```
+
+## TypeScript Best Practices
+
+1. **Use Strict TypeScript:** enable strict mode in tsconfig.json.
+2. **Define Interfaces:** create clear interface definitions for all data structures.
+3. **Avoid `any`:** use proper types or `unknown` instead of `any`.
+4. **Zod for Runtime Validation:** use Zod schemas to validate external data.
+5. **Type Guards:** create type guard functions for complex type checking.
+6. **Error Handling:** always use try-catch with proper error type checking.
+7. **Null Safety:** use optional chaining (`?.`) and nullish coalescing (`??`).
+
+```typescript
+// Good: Type-safe with Zod and interfaces
+interface UserResponse {
+  id: string;
+  name: string;
+  email: string;
+  team?: string;
+  active: boolean;
+}
+
+const UserSchema = z.object({
+  id: z.string(),
+  name: z.string(),
+  email: z.string().email(),
+  team: z.string().optional(),
+  active: z.boolean()
+});
+
+type User = z.infer<typeof UserSchema>;
+
+async function getUser(id: string): Promise<User> {
+  const data = await apiCall(`/users/${id}`);
+  return UserSchema.parse(data);  // Runtime validation
+}
+
+// Bad: Using any
+async function getUser(id: string): Promise<any> {
+  return await apiCall(`/users/${id}`);  // No type safety
+}
+```
+
+## Package Configuration
+
+### package.json
+
+```json
+{
+  "name": "{service}-mcp-server",
+  "version": "1.0.0",
+  "description": "MCP server for {Service} API integration",
+  "type": "module",
+  "main": "dist/index.js",
+  "scripts": {
+    "start": "node dist/index.js",
+    "dev": "tsx watch src/index.ts",
+    "build": "tsc",
+    "clean": "rm -rf dist"
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.6.1",
+    "axios": "^1.7.9",
+    "zod": "^3.23.8"
+  },
+  "devDependencies": {
+    "@types/node": "^22.10.0",
+    "tsx": "^4.19.2",
+    "typescript": "^5.7.2"
+  }
+}
+```
+
+### tsconfig.json
+
+```json
+{
+  "compilerOptions": {
+    "target": "ES2022",
+    "module": "Node16",
+    "moduleResolution": "Node16",
+    "lib": ["ES2022"],
+    "outDir": "./dist",
+    "rootDir": "./src",
+    "strict": true,
+    "esModuleInterop": true,
+    "skipLibCheck": true,
+    "forceConsistentCasingInFileNames": true,
+    "declaration": true,
+    "declarationMap": true,
+    "sourceMap": true,
+    "allowSyntheticDefaultImports": true
+  },
+  "include": ["src/**/*"],
+  "exclude": ["node_modules", "dist"]
+}
+```
+
+## Complete Example
+
+```typescript
+#!/usr/bin/env node
+/**
+ * MCP Server for Example Service.
+ *
+ * This server provides tools to interact with Example API, including user search,
+ * project management, and data export capabilities.
+ */
+
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
+import { z } from "zod";
+import axios, { AxiosError } from "axios";
+
+// Constants
+const API_BASE_URL = "https://api.example.com/v1";
+const CHARACTER_LIMIT = 25000;
+
+// Enums
+enum ResponseFormat {
+  MARKDOWN = "markdown",
+  JSON = "json"
+}
+
+// Zod schemas
+const UserSearchInputSchema = z.object({
+  query: z.string()
+    .min(2, "Query must be at least 2 characters")
+    .max(200, "Query must not exceed 200 characters")
+    .describe("Search string to match against names/emails"),
+  limit: z.number()
+    .int()
+    .min(1)
+    .max(100)
+    .default(20)
+    .describe("Maximum results to return"),
+  offset: z.number()
+    .int()
+    .min(0)
+    .default(0)
+    .describe("Number of results to skip for pagination"),
+  response_format: z.nativeEnum(ResponseFormat)
+    .default(ResponseFormat.MARKDOWN)
+    .describe("Output format: 'markdown' for human-readable or 'json' for machine-readable")
+}).strict();
+
+type UserSearchInput = z.infer<typeof UserSearchInputSchema>;
+
+// Shared utility functions
+async function makeApiRequest<T>(
+  endpoint: string,
+  method: "GET" | "POST" | "PUT" | "DELETE" = "GET",
+  data?: any,
+  params?: any
+): Promise<T> {
+  try {
+    const response = await axios({
+      method,
+      url: `${API_BASE_URL}/${endpoint}`,
+      data,
+      params,
+      timeout: 30000,
+      headers: {
+        "Content-Type": "application/json",
+        "Accept": "application/json"
+      }
+    });
+    return response.data;
+  } catch (error) {
+    throw error;
+  }
+}
+
+function handleApiError(error: unknown): string {
+  if (error instanceof AxiosError) {
+    if (error.response) {
+      switch (error.response.status) {
+        case 404:
+          return "Error: Resource not found. Please check the ID is correct.";
+        case 403:
+          return "Error: Permission denied. You don't have access to this resource.";
+        case 429:
+          return "Error: Rate limit exceeded. Please wait before making more requests.";
+        default:
+          return `Error: API request failed with status ${error.response.status}`;
+      }
+    } else if (error.code === "ECONNABORTED") {
+      return "Error: Request timed out. Please try again.";
+    }
+  }
+  return `Error: Unexpected error occurred: ${error instanceof Error ? error.message : String(error)}`;
+}
+
+// Create MCP server instance
+const server = new McpServer({
+  name: "example-mcp",
+  version: "1.0.0"
+});
+
+// Register tools
+server.registerTool(
+  "example_search_users",
+  {
+    title: "Search Example Users",
+    description: `[Full description as shown above]`,
+    inputSchema: UserSearchInputSchema,
+    annotations: {
+      readOnlyHint: true,
+      destructiveHint: false,
+      idempotentHint: true,
+      openWorldHint: true
+    }
+  },
+  async (params: UserSearchInput) => {
+    // Implementation as shown above
+  }
+);
+
+// Main function
+// For stdio (local):
+async function runStdio() {
+  if (!process.env.EXAMPLE_API_KEY) {
+    console.error("ERROR: EXAMPLE_API_KEY environment variable is required");
+    process.exit(1);
+  }
+
+  const transport = new StdioServerTransport();
+  await server.connect(transport);
+  console.error("MCP server running via stdio");
+}
+
+// For streamable HTTP (remote):
+async function runHTTP() {
+  if (!process.env.EXAMPLE_API_KEY) {
+    console.error("ERROR: EXAMPLE_API_KEY environment variable is required");
+    process.exit(1);
+  }
+
+  const app = express();
+  app.use(express.json());
+
+  app.post('/mcp', async (req, res) => {
+    const transport = new StreamableHTTPServerTransport({
+      sessionIdGenerator: undefined,
+      enableJsonResponse: true
+    });
+    res.on('close', () => transport.close());
+    await server.connect(transport);
+    await transport.handleRequest(req, res, req.body);
+  });
+
+  const port = parseInt(process.env.PORT || '3000');
+  app.listen(port, () => {
+    console.error(`MCP server running on http://localhost:${port}/mcp`);
+  });
+}
+
+// Choose transport based on environment
+const transport = process.env.TRANSPORT || 'stdio';
+if (transport === 'http') {
+  runHTTP().catch(error => {
+    console.error("Server error:", error);
+    process.exit(1);
+  });
+} else {
+  runStdio().catch(error => {
+    console.error("Server error:", error);
+    process.exit(1);
+  });
+}
+```
+
+Advanced MCP features (resources, transport, notifications), build/run commands, and the quality checklist are in `14-node-advanced-and-checklist.md`.
+
+---
+<!-- module: 14-node-advanced-and-checklist.md -->
+
+# Node/TypeScript — Advanced Features, Build & Quality Checklist
+
+Continues `13-node-implementation.md`. Advanced MCP features, building/running, and the finalization checklist.
+
+## Advanced MCP Features
+
+### Resource Registration
+
+Expose data as resources for efficient, URI-based access:
+
+```typescript
+import { ResourceTemplate } from "@modelcontextprotocol/sdk/types.js";
+
+// Register a resource with URI template
+server.registerResource(
+  {
+    uri: "file://documents/{name}",
+    name: "Document Resource",
+    description: "Access documents by name",
+    mimeType: "text/plain"
+  },
+  async (uri: string) => {
+    // Extract parameter from URI
+    const match = uri.match(/^file:\/\/documents\/(.+)$/);
+    if (!match) {
+      throw new Error("Invalid URI format");
+    }
+
+    const documentName = match[1];
+    const content = await loadDocument(documentName);
+
+    return {
+      contents: [{
+        uri,
+        mimeType: "text/plain",
+        text: content
+      }]
+    };
+  }
+);
+
+// List available resources dynamically
+server.registerResourceList(async () => {
+  const documents = await getAvailableDocuments();
+  return {
+    resources: documents.map(doc => ({
+      uri: `file://documents/${doc.name}`,
+      name: doc.name,
+      mimeType: "text/plain",
+      description: doc.description
+    }))
+  };
+});
+```
+
+**When to use Resources vs Tools:**
+- **Resources:** for data access with simple URI-based parameters
+- **Tools:** for complex operations requiring validation and business logic
+- **Resources:** when data is relatively static or template-based
+- **Tools:** when operations have side effects or complex workflows
+
+### Transport Options
+
+The TypeScript SDK supports two main transport mechanisms:
+
+#### Streamable HTTP (Recommended for Remote Servers)
+
+```typescript
+import { StreamableHTTPServerTransport } from "@modelcontextprotocol/sdk/server/streamableHttp.js";
+import express from "express";
+
+const app = express();
+app.use(express.json());
+
+app.post('/mcp', async (req, res) => {
+  // Create new transport for each request (stateless, prevents request ID collisions)
+  const transport = new StreamableHTTPServerTransport({
+    sessionIdGenerator: undefined,
+    enableJsonResponse: true
+  });
+
+  res.on('close', () => transport.close());
+
+  await server.connect(transport);
+  await transport.handleRequest(req, res, req.body);
+});
+
+app.listen(3000);
+```
+
+#### stdio (For Local Integrations)
+
+```typescript
+import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
+
+const transport = new StdioServerTransport();
+await server.connect(transport);
+```
+
+**Transport selection:**
+- **Streamable HTTP:** web services, remote access, multiple clients
+- **stdio:** command-line tools, local development, subprocess integration
+
+### Notification Support
+
+Notify clients when server state changes:
+
+```typescript
+// Notify when tools list changes
+server.notification({
+  method: "notifications/tools/list_changed"
+});
+
+// Notify when resources change
+server.notification({
+  method: "notifications/resources/list_changed"
+});
+```
+
+Use notifications sparingly — only when server capabilities genuinely change.
+
+## Code Best Practices
+
+### Code Composability and Reusability
+
+Prioritize composability and code reuse (the general rule is in `00-core.md`): extract common functionality into reusable helper functions, shared API clients, centralized error handling, composable business logic, and shared markdown/JSON field-selection & formatting. NEVER copy-paste similar code between tools; if you write similar logic twice, extract it. Share pagination, filtering, field selection, and formatting; centralize authentication/authorization.
+
+## Building and Running
+
+Always build your TypeScript code before running:
+
+```bash
+# Build the project
+npm run build
+
+# Run the server
+npm start
+
+# Development with auto-reload
+npm run dev
+```
+
+Always ensure `npm run build` completes successfully before considering the implementation complete.
+
+## Quality Checklist
+
+Before finalizing your Node/TypeScript MCP server implementation, ensure:
+
+### Strategic Design
+- [ ] Tools enable complete workflows, not just API endpoint wrappers
+- [ ] Tool names reflect natural task subdivisions
+- [ ] Response formats optimize for agent context efficiency
+- [ ] Human-readable identifiers used where appropriate
+- [ ] Error messages guide agents toward correct usage
+
+### Implementation Quality
+- [ ] FOCUSED IMPLEMENTATION: Most important and valuable tools implemented
+- [ ] All tools registered using `registerTool` with complete configuration
+- [ ] All tools include `title`, `description`, `inputSchema`, and `annotations`
+- [ ] Annotations correctly set (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
+- [ ] All tools use Zod schemas for runtime input validation with `.strict()` enforcement
+- [ ] All Zod schemas have proper constraints and descriptive error messages
+- [ ] All tools have comprehensive descriptions with explicit input/output types
+- [ ] Descriptions include return value examples and complete schema documentation
+- [ ] Error messages are clear, actionable, and educational
+
+### TypeScript Quality
+- [ ] TypeScript interfaces are defined for all data structures
+- [ ] Strict TypeScript is enabled in tsconfig.json
+- [ ] No use of `any` type - use `unknown` or proper types instead
+- [ ] All async functions have explicit Promise<T> return types
+- [ ] Error handling uses proper type guards (e.g., `axios.isAxiosError`, `z.ZodError`)
+
+### Advanced Features (where applicable)
+- [ ] Resources registered for appropriate data endpoints
+- [ ] Appropriate transport configured (stdio or streamable HTTP)
+- [ ] Notifications implemented for dynamic server capabilities
+- [ ] Type-safe with SDK interfaces
+
+### Project Configuration
+- [ ] Package.json includes all necessary dependencies
+- [ ] Build script produces working JavaScript in dist/ directory
+- [ ] Main entry point is properly configured as dist/index.js
+- [ ] Server name follows format: `{service}-mcp-server`
+- [ ] tsconfig.json properly configured with strict mode
+
+### Code Quality
+- [ ] Pagination is properly implemented where applicable
+- [ ] Large responses check CHARACTER_LIMIT constant and truncate with clear messages
+- [ ] Filtering options are provided for potentially large result sets
+- [ ] All network operations handle timeouts and connection errors gracefully
+- [ ] Common functionality is extracted into reusable functions
+- [ ] Return types are consistent across similar operations
+
+### Testing and Build
+- [ ] `npm run build` completes successfully without errors
+- [ ] dist/index.js created and executable
+- [ ] Server runs: `node dist/index.js --help`
+- [ ] All imports resolve correctly
+- [ ] Sample tool calls work as expected
+
+---
+<!-- module: 15-evaluation-design.md -->
+
+# Evaluations — Designing Questions (Phase 4)
+
+Create comprehensive evaluations that test whether LLMs can effectively use your MCP server to answer realistic, complex questions using ONLY the tools provided. Running the evaluation harness is covered in `16-evaluation-running.md`.
+
+## Purpose
+
+The measure of quality of an MCP server is NOT how well or comprehensively the server implements tools, but how well these implementations (input/output schemas, docstrings/descriptions, functionality) enable LLMs — with no other context and access ONLY to the MCP server — to answer realistic and difficult questions.
+
+## Overview & Requirements
+
+Create **10 human-readable questions** requiring ONLY READ-ONLY, INDEPENDENT, NON-DESTRUCTIVE, and IDEMPOTENT operations to answer. Each question should be:
+- Realistic
+- Clear and concise
+- Unambiguous
+- Complex, requiring potentially dozens of tool calls or steps
+- Answerable with a single, verifiable value that you identify in advance
+
+The four-step creation process (referenced from the workflow): (1) **Tool Inspection** — list available tools and understand their capabilities; (2) **Content Exploration** — use READ-ONLY operations to explore available data; (3) **Question Generation** — create 10 complex, realistic questions; (4) **Answer Verification** — solve each question yourself to verify answers.
+
+## Question Guidelines
+
+### Core Requirements
+
+1. **Questions MUST be independent** — each should NOT depend on the answer to any other question, and should not assume prior write operations from processing another question.
+2. **Questions MUST require ONLY NON-DESTRUCTIVE AND IDEMPOTENT tool use** — should not instruct or require modifying state to arrive at the correct answer.
+3. **Questions must be REALISTIC, CLEAR, CONCISE, and COMPLEX** — must require another LLM to use multiple (potentially dozens of) tools or steps to answer.
+
+### Complexity and Depth
+
+4. **Questions must require deep exploration** — consider multi-hop questions requiring multiple sub-questions and sequential tool calls; each step should benefit from information found in previous steps.
+5. **Questions may require extensive paging** — may need paging through multiple pages of results; may require querying old data (1–2 years out-of-date) to find niche information; the questions must be DIFFICULT.
+6. **Questions must require deep understanding** — rather than surface-level knowledge; may pose complex ideas as True/False questions requiring evidence; may use multiple-choice format where the LLM must search different hypotheses.
+7. **Questions must not be solvable with straightforward keyword search** — do not include specific keywords from the target content; use synonyms, related concepts, or paraphrases; require multiple searches, analyzing multiple related items, extracting context, then deriving the answer.
+
+### Tool Testing
+
+8. **Questions should stress-test tool return values** — may elicit tools returning large JSON objects or lists that overwhelm the LLM; should require understanding multiple modalities of data (IDs and names; timestamps and datetimes — months, days, years, seconds; file IDs, names, extensions, mimetypes; URLs, GIDs, etc.); should probe the tool's ability to return all useful forms of data.
+9. **Questions should MOSTLY reflect real human use cases** — the kinds of information-retrieval tasks that humans assisted by an LLM would care about.
+10. **Questions may require dozens of tool calls** — this challenges LLMs with limited context and encourages MCP server tools to reduce information returned.
+11. **Include ambiguous questions** — may be ambiguous OR require difficult decisions on which tools to call; force the LLM to potentially make mistakes or misinterpret; ensure that despite AMBIGUITY, there is STILL A SINGLE VERIFIABLE ANSWER.
+
+### Stability
+
+12. **Questions must be designed so the answer DOES NOT CHANGE** — do not ask questions that rely on dynamic "current state." For example, do not count: number of reactions to a post, number of replies to a thread, number of members in a channel.
+13. **DO NOT let the MCP server RESTRICT the kinds of questions you create** — create challenging and complex questions; some may not be solvable with the available tools; questions may require specific output formats (datetime vs. epoch time, JSON vs. MARKDOWN); questions may require dozens of tool calls.
+
+## Answer Guidelines
+
+### Verification
+
+1. **Answers must be VERIFIABLE via direct string comparison.** If the answer can be written in many formats, clearly specify the output format in the QUESTION (e.g., "Use YYYY/MM/DD.", "Respond True or False.", "Answer A, B, C, or D and nothing else."). Answer should be a single verifiable value such as: user ID, user name, display name, first name, last name; channel ID, channel name; message ID, string; URL, title; numerical quantity; timestamp, datetime; boolean (True/False); email address, phone number; file ID, file name, file extension; multiple choice answer. Answers must not require special formatting or complex, structured output. Answer will be verified using DIRECT STRING COMPARISON.
+
+### Readability
+
+2. **Answers should generally prefer HUMAN-READABLE formats** — names, first name, last name, datetime, file name, message string, URL, yes/no, true/false, a/b/c/d — rather than opaque IDs (though IDs are acceptable). The VAST MAJORITY of answers should be human-readable.
+
+### Stability
+
+3. **Answers must be STABLE/STATIONARY** — look at old content (conversations that have ended, projects that have launched, questions answered); create questions based on "closed" concepts that will always return the same answer; questions may ask to consider a fixed time window to insulate from non-stationary answers; rely on context UNLIKELY to change. Example: if finding a paper name, be SPECIFIC enough so the answer is not confused with papers published later.
+4. **Answers must be CLEAR and UNAMBIGUOUS** — designed so there is a single, clear answer derivable from the MCP server tools.
+
+### Diversity
+
+5. **Answers must be DIVERSE** — a single verifiable value in diverse modalities and formats. User concept: user ID, user name, display name, first name, last name, email address, phone number. Channel concept: channel ID, channel name, channel topic. Message concept: message ID, message string, timestamp, month, day, year.
+6. **Answers must NOT be complex structures** — not a list of values, not a complex object, not a list of IDs or strings, not natural language text — UNLESS the answer can be straightforwardly verified using DIRECT STRING COMPARISON and can be realistically reproduced (unlikely that an LLM would return the same list in any other order or format).
+
+## Evaluation Process
+
+1. **Documentation Inspection** — read the target API docs to understand available endpoints and functionality; if ambiguity exists, fetch additional info from the web; parallelize as much as possible; ensure each subagent is ONLY examining documentation from the file system or web.
+2. **Tool Inspection** — list the tools available in the MCP server; inspect input/output schemas, docstrings, and descriptions WITHOUT calling the tools at this stage.
+3. **Developing Understanding** — repeat steps 1 & 2, iterating multiple times; think about the tasks you want to create and refine understanding; at NO stage READ the code of the MCP server implementation itself; use intuition to create reasonable, realistic, but VERY challenging tasks.
+4. **Read-Only Content Inspection** — USE the MCP server tools with READ-ONLY, NON-DESTRUCTIVE operations ONLY to identify specific content (users, channels, messages, projects, tasks) for realistic questions. Do NOT call tools that modify state. Do NOT read the server's code. Parallelize with individual sub-agents pursuing independent explorations (each performing only read-only, non-destructive, idempotent operations). BE CAREFUL: some tools may return LOTS OF DATA and exhaust context — make INCREMENTAL, SMALL, TARGETED calls; in all tool call requests use the `limit` parameter (<10); use pagination.
+5. **Task Generation** — create 10 human-readable questions an LLM can answer with the MCP server, following all question and answer guidelines above.
+
+## Output Format
+
+Each QA pair consists of a question and an answer, in an XML file:
+
+```xml
+<evaluation>
+   <qa_pair>
+      <question>Find the project created in Q2 2024 with the highest number of completed tasks. What is the project name?</question>
+      <answer>Website Redesign</answer>
+   </qa_pair>
+   <qa_pair>
+      <question>Search for issues labeled as "bug" that were closed in March 2024. Which user closed the most issues? Provide their username.</question>
+      <answer>sarah_dev</answer>
+   </qa_pair>
+   <qa_pair>
+      <question>Look for pull requests that modified files in the /api directory and were merged between January 1 and January 31, 2024. How many different contributors worked on these PRs?</question>
+      <answer>7</answer>
+   </qa_pair>
+   <qa_pair>
+      <question>Find the repository with the most stars that was created before 2023. What is the repository name?</question>
+      <answer>data-pipeline</answer>
+   </qa_pair>
+</evaluation>
+```
+
+A single-pair illustration of the same structure:
+
+```xml
+<evaluation>
+  <qa_pair>
+    <question>Find discussions about AI model launches with animal codenames. One model needed a specific safety designation that uses the format ASL-X. What number X was being determined for the model named after a spotted wild cat?</question>
+    <answer>3</answer>
+  </qa_pair>
+<!-- More qa_pairs... -->
+</evaluation>
+```
+
+## Examples
+
+### Good Questions
+
+**Example 1 — Multi-hop question requiring deep exploration (GitHub MCP):**
+```xml
+<qa_pair>
+   <question>Find the repository that was archived in Q3 2023 and had previously been the most forked project in the organization. What was the primary programming language used in that repository?</question>
+   <answer>Python</answer>
+</qa_pair>
+```
+Good because: requires multiple searches to find archived repositories; needs to identify which had the most forks before archival; requires examining repository details for the language; answer is a simple verifiable value; based on historical (closed) data that won't change.
+
+**Example 2 — Requires understanding context without keyword matching (Project Management MCP):**
+```xml
+<qa_pair>
+   <question>Locate the initiative focused on improving customer onboarding that was completed in late 2023. The project lead created a retrospective document after completion. What was the lead's role title at that time?</question>
+   <answer>Product Manager</answer>
+</qa_pair>
+```
+Good because: doesn't use the specific project name; requires finding completed projects from a specific timeframe; needs to identify the project lead and their role; requires understanding context from retrospective documents; answer is human-readable and stable; based on completed work.
+
+**Example 3 — Complex aggregation requiring multiple steps (Issue Tracker MCP):**
+```xml
+<qa_pair>
+   <question>Among all bugs reported in January 2024 that were marked as critical priority, which assignee resolved the highest percentage of their assigned bugs within 48 hours? Provide the assignee's username.</question>
+   <answer>alex_eng</answer>
+</qa_pair>
+```
+Good because: requires filtering bugs by date, priority, and status; needs to group by assignee and calculate resolution rates; requires understanding timestamps to determine 48-hour windows; tests pagination; answer is a single username; based on historical data.
+
+**Example 4 — Requires synthesis across multiple data types (CRM MCP):**
+```xml
+<qa_pair>
+   <question>Find the account that upgraded from the Starter to Enterprise plan in Q4 2023 and had the highest annual contract value. What industry does this account operate in?</question>
+   <answer>Healthcare</answer>
+</qa_pair>
+```
+Good because: requires understanding subscription tier changes; needs to identify upgrade events in a specific timeframe; requires comparing contract values; must access account industry information; answer is simple and verifiable; based on completed historical transactions.
+
+### Poor Questions
+
+**Example 1 — Answer changes over time:**
+```xml
+<qa_pair>
+   <question>How many open issues are currently assigned to the engineering team?</question>
+   <answer>47</answer>
+</qa_pair>
+```
+Poor because: the answer changes as issues are created, closed, or reassigned; not based on stable data; relies on dynamic "current state."
+
+**Example 2 — Too easy with keyword search:**
+```xml
+<qa_pair>
+   <question>Find the pull request with title "Add authentication feature" and tell me who created it.</question>
+   <answer>developer123</answer>
+</qa_pair>
+```
+Poor because: solvable with a straightforward keyword search for the exact title; doesn't require deep exploration or understanding; no synthesis or analysis needed.
+
+**Example 3 — Ambiguous answer format:**
+```xml
+<qa_pair>
+   <question>List all the repositories that have Python as their primary language.</question>
+   <answer>repo1, repo2, repo3, data-pipeline, ml-tools</answer>
+</qa_pair>
+```
+Poor because: the answer is a list that could be returned in any order; difficult to verify with direct string comparison; an LLM might format differently (JSON array, comma-separated, newline-separated); better to ask for a specific aggregate (count) or superlative (most stars).
+
+## Verification Process
+
+After creating evaluations:
+1. **Examine the XML file** to understand the schema.
+2. **Load each task instruction** and, in parallel using the MCP server and tools, identify the correct answer by attempting to solve the task YOURSELF.
+3. **Flag any operations** that require WRITE or DESTRUCTIVE operations.
+4. **Accumulate all CORRECT answers** and replace any incorrect answers in the document.
+5. **Remove any `<qa_pair>`** that requires WRITE or DESTRUCTIVE operations.
+
+Parallelize solving tasks to avoid running out of context, then accumulate all answers and make changes to the file at the end.
+
+## Tips for Quality Evaluations
+
+1. **Think Hard and Plan Ahead** before generating tasks.
+2. **Parallelize Where Opportunity Arises** to speed up the process and manage context.
+3. **Focus on Realistic Use Cases** that humans would actually want to accomplish.
+4. **Create Challenging Questions** that test the limits of the MCP server's capabilities.
+5. **Ensure Stability** by using historical data and closed concepts.
+6. **Verify Answers** by solving the questions yourself using the MCP server tools.
+7. **Iterate and Refine** based on what you learn during the process.
+
+---
+<!-- module: 16-evaluation-running.md -->
+
+# Evaluations — Running the Harness
+
+After creating your evaluation file (see `15-evaluation-design.md`), use the provided evaluation harness (`scripts/evaluation.py`) to test your MCP server.
+
+## Setup
+
+1. **Install Dependencies**
+   ```bash
+   pip install -r scripts/requirements.txt
+   ```
+   Or install manually:
+   ```bash
+   pip install anthropic mcp
+   ```
+
+2. **Set API Key**
+   ```bash
+   export ANTHROPIC_API_KEY=your_api_key_here
+   ```
+
+## Evaluation File Format
+
+Evaluation files use XML format with `<qa_pair>` elements:
+
+```xml
+<evaluation>
+   <qa_pair>
+      <question>Find the project created in Q2 2024 with the highest number of completed tasks. What is the project name?</question>
+      <answer>Website Redesign</answer>
+   </qa_pair>
+   <qa_pair>
+      <question>Search for issues labeled as "bug" that were closed in March 2024. Which user closed the most issues? Provide their username.</question>
+      <answer>sarah_dev</answer>
+   </qa_pair>
+</evaluation>
+```
+
+## Running Evaluations
+
+The evaluation script (`scripts/evaluation.py`) supports three transport types.
+
+**Important:**
+- **stdio transport:** the evaluation script automatically launches and manages the MCP server process for you. Do not run the server manually.
+- **sse/http transports:** you must start the MCP server separately before running the evaluation. The script connects to the already-running server at the specified URL.
+
+### 1. Local STDIO Server
+
+For locally-run MCP servers (script launches the server automatically):
+
+```bash
+python scripts/evaluation.py \
+  -t stdio \
+  -c python \
+  -a my_mcp_server.py \
+  evaluation.xml
+```
+
+With environment variables:
+```bash
+python scripts/evaluation.py \
+  -t stdio \
+  -c python \
+  -a my_mcp_server.py \
+  -e API_KEY=abc123 \
+  -e DEBUG=true \
+  evaluation.xml
+```
+
+### 2. Server-Sent Events (SSE)
+
+For SSE-based MCP servers (you must start the server first):
+
+```bash
+python scripts/evaluation.py \
+  -t sse \
+  -u https://example.com/mcp \
+  -H "Authorization: Bearer token123" \
+  -H "X-Custom-Header: value" \
+  evaluation.xml
+```
+
+### 3. HTTP (Streamable HTTP)
+
+For HTTP-based MCP servers (you must start the server first):
+
+```bash
+python scripts/evaluation.py \
+  -t http \
+  -u https://example.com/mcp \
+  -H "Authorization: Bearer token123" \
+  evaluation.xml
+```
+
+## Command-Line Options
+
+```
+usage: evaluation.py [-h] [-t {stdio,sse,http}] [-m MODEL] [-c COMMAND]
+                     [-a ARGS [ARGS ...]] [-e ENV [ENV ...]] [-u URL]
+                     [-H HEADERS [HEADERS ...]] [-o OUTPUT]
+                     eval_file
+
+positional arguments:
+  eval_file             Path to evaluation XML file
+
+optional arguments:
+  -h, --help            Show help message
+  -t, --transport       Transport type: stdio, sse, or http (default: stdio)
+  -m, --model           Claude model to use (default: claude-3-7-sonnet-20250219)
+  -o, --output          Output file for report (default: print to stdout)
+
+stdio options:
+  -c, --command         Command to run MCP server (e.g., python, node)
+  -a, --args            Arguments for the command (e.g., server.py)
+  -e, --env             Environment variables in KEY=VALUE format
+
+sse/http options:
+  -u, --url             MCP server URL
+  -H, --header          HTTP headers in 'Key: Value' format
+```
+
+## Output
+
+The evaluation script generates a detailed report including:
+
+- **Summary Statistics:** Accuracy (correct/total); Average task duration; Average tool calls per task; Total tool calls.
+- **Per-Task Results:** Prompt and expected response; Actual response from the agent; Whether the answer was correct (✅/❌); Duration and tool call details; Agent's summary of its approach; Agent's feedback on the tools.
+
+### Save Report to File
+
+```bash
+python scripts/evaluation.py \
+  -t stdio \
+  -c python \
+  -a my_server.py \
+  -o evaluation_report.md \
+  evaluation.xml
+```
+
+## Complete Example Workflow
+
+1. **Create your evaluation file** (`my_evaluation.xml`):
+```xml
+<evaluation>
+   <qa_pair>
+      <question>Find the user who created the most issues in January 2024. What is their username?</question>
+      <answer>alice_developer</answer>
+   </qa_pair>
+   <qa_pair>
+      <question>Among all pull requests merged in Q1 2024, which repository had the highest number? Provide the repository name.</question>
+      <answer>backend-api</answer>
+   </qa_pair>
+   <qa_pair>
+      <question>Find the project that was completed in December 2023 and had the longest duration from start to finish. How many days did it take?</question>
+      <answer>127</answer>
+   </qa_pair>
+</evaluation>
+```
+
+2. **Install dependencies**:
+```bash
+pip install -r scripts/requirements.txt
+export ANTHROPIC_API_KEY=your_api_key
+```
+
+3. **Run evaluation**:
+```bash
+python scripts/evaluation.py \
+  -t stdio \
+  -c python \
+  -a github_mcp_server.py \
+  -e GITHUB_TOKEN=ghp_xxx \
+  -o github_eval_report.md \
+  my_evaluation.xml
+```
+
+4. **Review the report** in `github_eval_report.md` to: see which questions passed/failed; read the agent's feedback on your tools; identify areas for improvement; iterate on your MCP server design.
+
+## Troubleshooting
+
+### Connection Errors
+- **STDIO:** verify the command and arguments are correct.
+- **SSE/HTTP:** check the URL is accessible and headers are correct.
+- Ensure any required API keys are set in environment variables or headers.
+
+### Low Accuracy
+If many evaluations fail:
+- Review the agent's feedback for each task.
+- Check if tool descriptions are clear and comprehensive.
+- Verify input parameters are well-documented.
+- Consider whether tools return too much or too little data.
+- Ensure error messages are actionable.
+
+### Timeout Issues
+If tasks are timing out:
+- Use a more capable model (e.g., `claude-3-7-sonnet-20250219`).
+- Check if tools are returning too much data.
+- Verify pagination is working correctly.
+- Consider simplifying complex questions.