Definition
MCP tool naming convention is the discipline of naming Model Context Protocol tools clearly and orthogonally (e.g., scavio.search vs scavio.reddit_search vs scavio.youtube_search) so agents pick the right tool by name + description alone, without prompt engineering hacks to force routing.
In Depth
When MCPs are wired with overlapping or generic names ('search', 'lookup', 'find'), the LLM coin-flips per prompt phrasing. The convention that works: namespace.action format (scavio.search, linear.create_issue, semble.search), action verbs distinct per tool (search vs reddit_search vs youtube_search), and descriptions that explicitly say 'use for X, NOT for Y'. Scavio's MCP exposes 6 distinctly-named tools so a downstream agent can route correctly without bespoke prompt engineering. Agent runtimes that auto-truncate tool names lose this discipline; pick MCPs with the namespace.action shape preserved.
Example Usage
Agent has scavio.search, scavio.reddit_search, scavio.youtube_search attached. User asks 'what's reddit saying about X'. LLM routes to scavio.reddit_search by name alone. Compare to 'web_search' + 'reddit_lookup' + 'find_videos' (overlapping verbs) — much harder to route consistently.
Platforms
MCP Tool Naming Convention is relevant across the following platforms, all accessible through Scavio's unified API:
Related Terms
Tool Affordance (Agent)
Tool affordance is the signal an LLM agent uses to decide whether to call a given tool: the tool's name, description tex...
Agent Routing Layer
An agent routing layer is the component (often custom code or a framework primitive like LangGraph) that sits between th...
MCP Routing Decision
An MCP routing decision is the branch an agent makes when it has multiple MCP servers connected and must choose one (or ...