mcp-tool-usage

Enforce a five-tier hierarchy for routing operations to MCP tools.

Updated Apr 24, 2026

Search Tags:#automation #workflow #cli #mcp #coding #tool-selection #five-tier

Ready to run

npx skills add https://github.com/michael-conrad/.opencode --skill mcp-tool-usage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcp-tool-usage
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/mcp-tool-usage
Command: npx skills add https://github.com/michael-conrad/.opencode --skill mcp-tool-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams consistently select the most appropriate tool for a given task by enforcing a five-tier priority hierarchy, reducing decision drift and tool misuse.

Core Features & Use Cases

Enforces a deterministic tool-selection policy across file ops, code search, notebooks, and CLI fallbacks.
Routes decisions to specialized MCP components based on operation type and context.
Provides a ready-to-use Quick Start that demonstrates selecting a tool for a typical file-read task.

Quick Start

Ask the system to select the optimal tool for a given task using the five-tier hierarchy.

Frequently Asked Questions about mcp-tool-usage

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

FAQPage Schema

How do I select the right MCP tool for file operations and code search?▼

Select the right MCP tool by applying a strict five-tier hierarchy that routes file operations, code search, and notebooks to specialized components before falling back to the CLI. This deterministic routing enforces primary and fallback tool definitions to prevent decision drift.

What is a five-tier hierarchy for tool selection in coding workflows?▼

A five-tier hierarchy for tool selection is a strict priority policy that validates coding operations against a deterministic routing sequence. It defines primary, fallback, and prohibited tools across file ops and CLI commands to reduce tool misuse and decision drift.

How do I enforce deterministic tool routing for CLI fallbacks in automation workflows?▼

Enforce deterministic tool routing for CLI fallbacks by validating every automation operation against a five-tier policy. This approach defines primary and prohibited MCP tools, ensuring fallbacks only trigger when higher-priority specialized tools are unavailable.

Does the five-tier tool-selection policy work with notebooks and CLI commands?▼

Yes, the five-tier tool-selection policy works with notebooks and CLI commands by validating operations against a deterministic hierarchy. It routes tasks to specialized MCP components based on context and operation type, treating CLI as a fallback tier.

What's the best way to prevent tool misuse across team coding workflows?▼

The best way to prevent tool misuse is to enforce a five-tier tool-selection policy that validates all coding operations against deterministic routing rules. Defining primary, fallback, and prohibited tools eliminates inconsistent decision drift across the team.

When should I not use automated tool routing for MCP operations?▼

You should not use automated tool routing when a task requires manual intervention outside the defined five-tier hierarchy, or when the deterministic policy lacks a specialized MCP component for a unique operation type. Strict validation prohibits non-compliant tool usage.