skills.rest
PoBruno
PoBrunoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

mcp-tool-schema

Define and validate MCP tool schemas with Zod inputs and ToolResult contracts.

6|Updated Jun 8, 2026
Search Tags:#typescript#testing#zod#mcp#tools#tool-schema
One-click install
npx skills add https://github.com/PoBruno/mcp-blender-agent --skill mcp-tool-schema
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-tool-schema
Source: https://github.com/PoBruno/mcp-blender-agent/tree/main/.claude/skills/mcp-tool-schema
Command: npx skills add https://github.com/PoBruno/mcp-blender-agent --skill mcp-tool-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This field provides a standardized approach for designing and registering MCP tools by defining required schemas, contracts, and tests to ensure consistency across the tool registry.

Core Features & Use Cases

  • Zod-based input schemas for every tool input with descriptive validation
  • Standard ToolResult payload structure including data, refs, nextSteps, and warnings
  • End-to-end guidance for tool files, Python handlers, and integration into the server
  • Comprehensive testing requirements covering happy paths, error codes, idempotency, and cleanup

Quick Start

Register a new MCP tool by following the checklist in this guide and wire it into Tools/src/index.ts and the corresponding handlers/tests.

Frequently Asked Questions about mcp-tool-schema

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

FAQPage Schema
How do I define and validate MCP tool schemas for a new tool?▼

To define MCP tool schemas, you use Zod-based input schemas for validation and a standard ToolResult payload structure including data, refs, nextSteps, and warnings. This enforces consistency across the tool registry.

What is a ToolResult contract in MCP tool development?▼

A ToolResult contract is a standardized payload structure for MCP tools that includes data, refs, nextSteps, and warnings. It ensures consistent output format across the tool registry.

How do I register a new MCP tool in TypeScript?▼

Register a new MCP tool by defining its Zod input schema, creating the Python handlers, wiring it into Tools/src/index.ts, and following the checklist for required tests and documentation.

What testing is required for MCP tool schemas?▼

MCP tool schema testing requires comprehensive coverage of happy paths, error codes, idempotency, and cleanup to ensure robust tool validation and performance.

Can I use Zod for MCP tool input validation?▼

Yes, Zod is the required library for defining input schemas for every MCP tool input, providing descriptive validation to ensure correct data types and structure.

What limitations exist when adding new tools to Tools/src/tools?▼

Adding tools requires adhering to strict required elements: Zod input schemas, ToolResult contracts, specific error codes, Python handlers, and documentation updates, leaving no room for unstructured tool definitions.

Related Skills

Explore More Software Engineering Skills→
jon23djon23d
3

zod-env

Validate environment variables at startup using Zod schemas in TypeScript projects.

Community
Intermediate
CenredJunCenredJun

agent-tool-builder

Design JSON tool schemas with input examples and error handling for LLM agents.

Community
Advanced
Piebald-AIPiebald-AI
216

mcp

Query usage statistics from Splitrail's MCP server.

Official
Advanced
yehezkieldioyehezkieldio

zod

Guide Zod schema validation and type inference in TypeScript codebases.

Community
Advanced