skills.rest
thistleknot
thistleknotCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

mcp-tool-registry

Discover, register, and route MCP tools across multiple servers.

Updated Apr 20, 2026
Search Tags:#routing#mcp#tool discovery#json schema#tool registry#tool versioning#aci design
One-click install
npx skills add https://github.com/thistleknot/skills --skill mcp-tool-registry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-tool-registry
Source: https://github.com/thistleknot/skills/tree/main/mcp-tool-registry
Command: npx skills add https://github.com/thistleknot/skills --skill mcp-tool-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of agents not having a reliable, discoverable, and well-described inventory of MCP tools to call, which leads to incorrect tool selection and broken tool-use workflows.

Core Features & Use Cases

  • MCP tool discovery and registration: Calls tools/list on one or more MCP servers to build an index of available tools and their input schemas.
  • ACI-first tool schema design: Establishes naming and description practices so agents can select and call tools correctly using high-signal metadata.
  • Runtime routing and governance-ready execution: Routes tool calls to the correct server instance and includes a trust-tier/guardian interception point to control execution.
  • Versioning guidance for tool evolution: Uses semver and version pinning rules so schema changes don’t silently break agents.

Quick Start

Ask an AI to design your MCP tools with consistent ACI descriptions and JSON input schemas, then implement a registry that discovers tools from your server(s) and routes each tool call to the right MCP host with trust-tier guarding.

Frequently Asked Questions about mcp-tool-registry

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

FAQPage Schema
How do I discover and register MCP tools from multiple servers?▼

MCP tool discovery and registration works by calling tools/list on one or more MCP servers to build a centralized index of available tools and their JSON input schemas. This registry serves as a universal agent-tool interface for reliable routing.

What is ACI design for MCP tool schemas?▼

ACI-first tool schema design establishes naming and description practices using high-signal metadata and JSON inputSchema definitions. This ensures agents can accurately select and call tools without incorrect tool selection or broken workflows.

How do I route MCP tool calls to the correct server at runtime?▼

Runtime routing directs tool calls to the correct MCP server instance by matching the tool name against the registry. It includes a trust-tier guardian interception point to control execution safely across multiple server URLs.

How does tool versioning work when evolving MCP tool schemas?▼

Tool versioning uses semver and version pinning rules so schema changes do not silently break agents. This ensures consistent tool evolution and registry refresh capabilities when managing multiple MCP server versions.

Why does my agent select the wrong MCP tool during workflows?▼

Incorrect tool selection happens when agents lack a reliable, discoverable inventory of well-described MCP tools. Applying ACI-focused tool descriptions and accurate JSON inputSchema definitions provides the high-signal metadata needed for correct selection.

Related Skills

Explore More Software Engineering Skills→
abhishekmmgnabhishekmmgn

mcp-tool-definition

Define MCP tools with mandatory inputSchema and optional outputSchema JSON schemas.

Community
Intermediate
InverterNetworkInverterNetwork

mcporter

Discover and execute MCP servers and tools via a unified CLI.

Official
Intermediate
khapn-2933khapn-2933

tkm:manage-mcp

Manages MCP servers for tool discovery, execution, and resource access.

Community
Advanced
truongnattruongnat

tool-discovery-skill

Detect local tools by capability and update .harness/TOOL_CONTEXT.md.

Community
Intermediate