Under the traditional MCP calling approach, intermediate data (such as a meeting recording transcript) enters the context twice—once when read and once when passed as a parameter—causing redundant token consumption