mcp-tool-checklist

Audit MCP tool implementations for compliance with pagination, filtering, and description conventions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jmagar/rust-bin --skill mcp-tool-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-tool-checklist
Source: https://github.com/jmagar/rust-bin/tree/main/.claude/skills/mcp-tool-checklist
Command: npx skills add https://github.com/jmagar/rust-bin --skill mcp-tool-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authoritative MCP tool design checklist to enforce token-consciousness rules, proper tool registration shapes, and a robust 4-element description template, preventing drift and unsafe implementations.

Core Features & Use Cases

  • Enforces domain-scoped tool definitions with standard ActionSpec and embedded help output.
  • Validates compliance with MCP conventions across pagination, field filtering, truncation, and output budgeting.
  • Serves as a reference during tool design, review, and integration to ensure safety, clarity, and catalog quality.

Quick Start

Run the checklist on a new or modified MCP tool to verify compliance before submission.

Frequently Asked Questions about mcp-tool-checklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit MCP tool implementations for convention compliance?

Auditing MCP tool implementations for convention compliance requires verifying pagination, field filtering, truncation, output budgeting, and transport configurations. This checklist validates tool registration shapes and enforces a 4-element description template to prevent drift.

What is a 4-element description template for MCP tool design?

A 4-element description template for MCP tool design is a standardized format ensuring tool descriptions provide consistent, clear, and safe documentation for catalog quality. It enforces domain-scoped definitions with standard ActionSpec and embedded help output.

How do I prevent prompt injection in MCP tool development?

Preventing prompt injection in MCP tool development requires implementing panic isolation and token-consciousness rules during the design phase. Applying an audit checklist verifies that tool definitions are domain-scoped and safely structured before submission.

Does MCP tooling require specific output budgeting and truncation rules?

MCP tooling requires specific output budgeting and truncation rules to enforce token-consciousness and prevent unsafe implementations. Validating compliance with these conventions ensures tools handle large datasets safely without exceeding token limits.

What is panic isolation in MCP tool compliance?

Panic isolation in MCP tool compliance is a safety mechanism verified during tool audits to ensure catastrophic failures are contained. The checklist validates that tool implementations properly isolate panics to maintain robust and safe catalog operations.

Can I use a checklist to verify MCP tool pagination and field filtering?

You can use a checklist to verify MCP tool pagination and field filtering by validating the tool implementation against MCP conventions. This ensures the tool correctly handles data segmentation and selective field retrieval for safe operations.