Help or Hurdle? Rethinking Model Context Protocol-Augmented Large Language Models
Wei Song, Haonan Zhong, Ziqi Ding, Jingling Xue, Yuekang Li · 2025 · arXiv
TL;DR
MCPGAUGE is introduced, the first comprehensive evaluation framework for probing LLM-MCP interactions along four key dimensions: proactivity (self-initiated tool use), compliance, effectiveness, effectiveness, and overhead (computational cost incurred).
Abstract
The Model Context Protocol (MCP) enables large language models (LLMs) to access external resources on demand. While commonly assumed to enhance performance, how LLMs actually leverage this capability remains poorly understood. We introduce MCPGAUGE, the first comprehensive evaluation framework for probing LLM-MCP interactions along four key dimensions: proactivity (self-initiated tool use), compliance (adherence to tool-use instructions), effectiveness (task performance post-integration), and overhead (computational cost incurred). MCPGAUGE comprises a 160-prompt suite and 25 datasets spanning knowledge comprehension, general reasoning, and code generation. Our large-scale evaluation, spanning six commercial LLMs, 30 MCP tool suites, and both one- and two-turn interaction settings, comprises around 20,000 API calls and over USD 6,000 in computational cost. This comprehensive study reveals four key findings that challenge prevailing assumptions about the effectiveness of MCP integration. These insights highlight critical limitations in current AI-tool integration and position MCPGAUGE as a principled benchmark for advancing controllable, tool-augmented LLMs.
Editorial notes
Introduces MCPGAUGE, the first comprehensive evaluation framework for LLM-MCP interactions along four dimensions: proactivity (self-initiated tool use), compliance (adherence to tool-use instructions), effectiveness (task performance post-integration), and overhead (computational cost). 160- prompt suite across 25 datasets covering knowledge comprehension, general reasoning, and code generation; evaluated on six commercial LLMs and 30 MCP tool suites with ~20,000 API calls. Findings challenge the prevailing assumption that MCP integration unambiguously helps. Relates to SAICA-KG failure modes: scope_creep, context_pollution, incomplete_execution. Cite as evidence that 'tool use' itself is a supervisable behavior, not just a capability.