tapps-tool-reference

The TappsMCP tool reference provides a complete, task-oriented guide for when to use each tool, covering session_start, quick_check, validate_changed, and score_file. It presents structured usage rules and examples to prevent tool misapplication during development workflows.

To start a TappsMCP workflow, use the session_start tool and reference the guide for managing project memory via the memory tool. The reference covers core and extended tools, offering clear guidance on when to engage each tool across design, development, and deployment phases.

Yes, TappsMCP includes extended tools like security_scan, dependency_scan, and dependency_graph for pipeline workflows. The reference guide details when to use these tools for impact analysis, dead code detection, and configuration validation across your projects.

The TappsMCP reference enforces an allowed-tools constraint to ensure correct tool usage. It provides structured examples and rules, helping you navigate limitations and avoid misapplication when running checklist validations or quality gates.

The reference distinguishes between quick_check for rapid checks and quality_gate or checklist for thorough validation. Use the guide to determine the correct tool based on your specific task, whether you are validating changed files or ensuring overall project quality.

Instead of looking up docs individually, the TappsMCP reference consolidates all tool definitions into a single structured guide. It covers core tools, extended tools, and usage rules, providing a complete comparison of when to use each tool across different project phases.