Only one tool is exposed, so there is no competing operation to confuse it with; its description clearly states it selects MCP tools and does not execute them. The purpose is unambiguous, though the set is too small to demonstrate real disambiguation.

mcp_select uses a readable snake_case verb form with a server prefix, and with only one tool there is no convention mixing. The name is understandable, though it does not follow a broader verb_noun pattern because no other tools exist.

A single tool is explicitly considered too few for the apparent scope; the server is a focused selector, but one operation leaves no room for related lifecycle actions. The score reflects the thin surface rather than poor quality.

The tool covers the core selection operation, but a selection service would typically also expose ways to inspect available tools, configure budget, or refresh the index. Those gaps are notable but not fatal for a minimal router.