MCP服务器架构模式：LLM工具设计指南

Very timely paper.

MCP servers need clear design patterns because LLMs get confused when too many tools or vague tools are shown.

This paper explains how MCP servers should be structured so LLM tools stay useful, safe, and manageable.

s MCP server design is not just normal API design, because the client is an LLM that chooses tools by reading plain-language descriptions.

It groups real MCP servers into 5 useful patterns, such as servers that expose data, run workflows, keep session state, combine many servers, or translate messy domain APIs.

The authors also warn about 4 common mistakes, especially giant all-purpose tools, vague tool descriptions, unsafe outside content, and slow tools that should return a job ID instead.

They tested the pattern labels on 54 extra servers, measured transport delay, and studied how tool accuracy changes as more tools are shown.

The key result is that too many visible tools hurt accuracy, with weaker models dropping below 90% between 10 and 15 tools.

Good MCP design is mostly about making the tool list small, clear, safe, and stable enough for LLMs to choose the right action.

Link – arxiv. org/abs/2606.30317

Title: "MCP Server Architecture Patterns for LLM-Integrated Applications"