Luyện nói tiếng Anh bằng Shadowing qua video: MCP Just Got a Whole Lot Better
Chọn chế độ luyện tập
Mỗi chế độ mở một phòng luyện tập toàn màn hình.
61 câu
Nếu các câu quá ngắn hoặc quá dài, hãy bấm Edit để chỉnh sửa.
1
MCP is blowing up right now.
2
Agents' usage of MCP is increasing exponentially and it's not showing any signs of slowing down.
3
But at the same time, many agents are now changing the way that they handle tools
4
and starting to take over responsibilities that used to belong to the server.
5
So what does all of this mean for the way that we build MCP servers?
6
Well, let's break it all down.
7
When MCP first hit the scene, one of the most common approaches for building MCP servers was
8
to just map each of your API endpoints to its own tool.
9
And by doing this, an agent was able to access the full range of your API surface area.
10
And this implementation worked, but it presented two major issues.
11
First, if your API had hundreds of endpoints, then that meant your MCP server had hundreds of tools.
12
And all of these tools would be loaded into the context window up front, meaning that before you even started your session, your context window could have been completely bloated by MCP tools.
13
And secondly, if you had lots of endpoints that were similar to each other, an agent might end up getting confused and not pick the right tool for the job.
14
In order to solve some of these problems, a lot of MCP servers adopted a layered tool call approach.
15
So now, instead of listing out hundreds of tool calls, you might just have two or three, You might have a tool to search all of the available endpoints,
16
a tool to inspect the definition of a specific endpoint, and a tool to execute the request.
17
This pattern has seen a lot of adoption, but this is now where the big change happens.
18
Traditionally, this pattern was implemented on the MCP server side.
19
But more recently, many MCP clients, especially many popular coding agents, are implementing this pattern on the client side.
20
The pattern is now called progressive tool discovery, and it's a recommended best practice for MCP clients.
21
In addition, a lot of these agents, like Codex or ClaudeCode, are implementing what's called programmatic tool calling, also known as code mode.
22
With code mode, instead of calling tools one at a time, the agent will go ahead and write a script that chains those tools together in a sandbox environment.
23
The script then runs in the sandbox, and then only the final result is returned back to the model.
24
Between progressive discovery handling tool call selection and then code mode handling tool composition,
25
the clients are now starting to take more ownership of the problems that servers originally were trying to solve.
26
So surely this means we can just go back to the
27
original method of doing a one-to-one mapping of API endpoints to tool calls, right?
28
Not quite.
29
While an agent certainly can accomplish everything it needs to just by having access to tools that represent every API endpoint,
30
that isn't necessarily always the most efficient way to interact with an API.
31
For any given API, there are often very common tasks or workflows that require stringing together multiple API calls.
32
And if an agent has to figure out that chain on its own every single time, that's a lot of wasted tokens.
33
And this is the same reason that SDKs exist.
34
They give you the raw endpoints but also bundle common workflows into single operations.
35
And we can apply that same idea to the tools that we expose through our MCP server.
36
So for example, with Neon, we have this idea of creating a branch.
37
But it turns out that creating a branch is actually three separate API calls under the hood.
38
You have to first create the branch itself, but then make a separate call to attach compute resources to the branch, and make a third call to get the connection string.
39
In the SDK, we bundle those three API calls into one method called createWithCompute.
40
So as this relates to our MCP server, in order to give MCP clients the most token-efficient path possible,
41
it's helpful to expose operations like this that they can take advantage of in some of these common use cases.
42
Of course, if your API is relatively simple and straightforward, a one-to-one mapping might be totally fine.
43
But for something like Neon, where there's some complexity in provisioning infrastructure,
44
these ergonomic shortcuts save the agent from making the same mistakes over and over again.
45
So at Neon, we have an SDK which is generated from from our open API spec.
46
So that way it covers every API endpoint.
47
But on top of that generated layer, we also have another thinner layer that adds the ergonomic methods that we were just talking about, things like create with compute.
48
From here, in order for this to be usable by agents, we need to convert all of these methods into tool calls.
49
So that's exactly what we did with a package that we call neon tools.
50
So that includes both the raw endpoints and the ergonomic workflows, all as tool calls.
51
And by virtue of pulling these tools out into a separate package, we're able to serve a few different use cases.
52
First and foremost, in the Neon MCP server, the server imports this package to surface all of these tools to any MCP client.
53
But on top of that, we can also take this package and build adapters around it for different agent frameworks.
54
So for example, we have adapters for both Mastra and Eve for anyone building custom agents with those frameworks.
55
And one more thing worth noting is that these tools are organized into categories, so that way you can scope down exactly which tools you want the agent to have access to.
56
All in all, the big idea here is that the server is controlling what tools are available,
57
but then the client handles discovering and executing those tools in whatever way it sees fit.
58
All of this is open source, so if you want to dive through the code and see exactly how everything is implemented, I'll have some links down in the description for you to check out.
59
ways that you're approaching building your own MCP server?
60
Let us know down in the comments.
61
Thank you so much for watching and I'll see you in the next one.
Tải Ứng Dụng
Mọi thứ bạn cần để nói trôi chảy
Chấm điểm AIChấm từng câu nói
Luyện IPAThành thạo mọi âm
Từ vựngMở rộng vốn từ
Game Từ vựngHọc qua chơi
FOR YOU
Video gợi ý
C11
143 câu
MCP vs API: The protocol every developer needs to know
Business EnglishUniversity StudentsWorking Adults
C11
309 câu
Claude Code: The Advanced Guide (99% of Devs Skip These Features)
Business EnglishUniversity StudentsWorking Adults
C112
25 câu
Introducing the Agents API
Business EnglishUniversity StudentsWorking Adults
C1117 câu
I've Changed My Opinion On DEVELOPERS Vibe Coding
Business EnglishUniversity StudentsWorking Adults
C16
49 câu
What Are Microservices Really All About? (And When Not To Use It)
Business EnglishUniversity StudentsWorking Adults
C14
78 câu
Connect Slack to Salesforce with Hosted MCP Servers | Salesforce Headless 360 Decoded
Business EnglishUniversity StudentsWorking Adults
C11
197 câu
Unreal Engine 5.8 - Experimental MCP Server Support Walkthrough | State of Unreal 2026
Business EnglishWorking Adults
C12
339 câu
Easy Migration from Postgres to Databricks Lakebase
Business EnglishUniversity StudentsWorking Adults
C14
58 câu
The mystery is solved... and the answer is 40x cheaper than Claude
American AccentBusiness EnglishUniversity StudentsWorking Adults
C11
25 câu
One Person. One System. Your Entire Growth Team
Business EnglishWorking Adults
C13
200 câu
CAP Theorem in System Design Interviews
Business EnglishInterview EnglishUniversity Students
C15
317 câu
Give Me 18 Minutes and I’ll Make you Dangerously Smart (with AI)
Business EnglishUniversity StudentsWorking Adults
Từ vựng và ghi chú luyện nói cho bài học này
Bài luyện nói trình độ C1 này dựa trên video “MCP Just Got a Whole Lot Better”. Những từ được nhắc lại nhiều nhất trong bài: tool, Mcp, agent, Api, server. Video này có 61 câu và 1064 từ để luyện shadowing. Phần lời nói dài 5:55. Người nói nói nhanh, khoảng 180 từ mỗi phút, nên sẽ có nhiều chỗ nối âm và nuốt âm. Chỉ 81% số từ nằm trong 3.000 từ tiếng Anh thông dụng nhất, nên từ vựng khá khó.
Từ vựng quan trọng trong video
9 từ khó nhất trong video, kèm phiên âm và nghĩa:
| Từ | Phiên âm | Nghĩa |
|---|---|---|
| endpoint danh từ | đầu mút, mút | |
| neon danh từ | /ˈniˌɑn/ | neon, nê-ông |
| sandbox danh từ | /ˈsæn(d).bɑks/ | hộp cát |
| bundle danh từ | /ˈbʌn.dl̩/ | chùm, bó |
| shortcut danh từ | /ˈʃɔːtkʌt/ | lối tắt, đường tắt |
| usable tính từ | /ˈjuː.zə.bəl/ | dùng được, khả dụng |
| inspect động từ | /ɪnˈspɛkt/ | kiểm tra |
| organize động từ | /ˈɔɹɡənaɪz/ | sắp xếp, tổ chức |
| interact động từ | /ɪn.təˈɹækt/ | tương tác |
Cụm động từ bạn sẽ nghe
| Từ | Nghĩa |
|---|---|
| blow up động từ | nổ |
| check out động từ | tính tiền, trả phòng |
Phát âm cần chú ý
Người nói dùng 5 dạng rút gọn, ví dụ I'll, isn't, we're. Hãy nói theo dạng ngắn đúng như bạn nghe.
- Âm “sh” và “zh”: exponentially /ɛkspə(ʊ)ˈnɛnʃəli/, shortcut /ˈʃɔːtkʌt/, speculation /ˌspɛk.jəˈleɪ.ʃən/, accomplish /əˈkɑm.plɪʃ/, traditionally /tɹəˈdɪʃ.ə.nə.li/
- Từ dài — đặt trọng âm cho đúng: exponentially /ɛkspə(ʊ)ˈnɛnʃəli/, programmatic /ˌpɹəʊ.ɡɹəˈmæt.ɪk/, speculation /ˌspɛk.jəˈleɪ.ʃən/, complexity /kəmˈplɛk.sɪ.ti/, traditionally /tɹəˈdɪʃ.ə.nə.li/
Những âm người Việt thường gặp khó:
- Cụm phụ âm cuối — đọc đủ từng âm, đừng nuốt âm cuối: sandbox /ˈsæn(d).bɑks/, inspect /ɪnˈspɛkt/, foremost /ˈfɔː.məʊst/, straightforward /ˌstɹeɪtˈfɔː(ɹ)wə(ɹ)d/, interact /ɪn.təˈɹækt/
- Âm /tʃ/, /dʒ/ và /ʒ/ — tiếng Việt không có, đừng đọc thành “ch” hay “gi”: attach /əˈtæt͡ʃ/, virtue /ˈvɝt͡ʃu/
- Âm /æ/ — mở miệng rộng hơn âm “e”: sandbox /ˈsæn(d).bɑks/, adapter /əˈdæptəɹ/, programmatic /ˌpɹəʊ.ɡɹəˈmæt.ɪk/, attach /əˈtæt͡ʃ/, interact /ɪn.təˈɹækt/
Cách luyện với video này
- Nghe hết video một lần, chưa cần nói, và ghi lại những từ bạn chưa biết.
- Bắt đầu ở tốc độ 0,75×, nói đuổi từng câu, rồi quay lại tốc độ bình thường khi đã quen.
- Ghi âm giọng mình rồi so với bản gốc, chú ý các từ như endpoint, neon, sandbox.
Phương Pháp Shadowing Là Gì?
Shadowing là kỹ thuật học ngôn ngữ có cơ sở khoa học, ban đầu được phát triển cho chương trình đào tạo phiên dịch viên chuyên nghiệp và được phổ biến rộng rãi bởi nhà đa ngôn ngữ học Dr. Alexander Arguelles. Nguyên lý cốt lõi đơn giản nhưng cực kỳ hiệu quả: bạn nghe tiếng Anh của người bản xứ và lặp lại to ngay lập tức — như một "cái bóng" (shadow) đuổi theo người nói với độ trễ chỉ 1–2 giây. Khác với luyện ngữ pháp hay học từ vựng bị động, Shadowing buộc não bộ và cơ miệng phải đồng thời xử lý và tái tạo ngôn ngữ thực tế. Các nghiên cứu khoa học xác nhận phương pháp này cải thiện đáng kể phát âm, ngữ điệu, nhịp điệu, nối âm, kỹ năng nghe và độ lưu loát khi nói — đặc biệt hiệu quả cho người luyện IELTS Speaking và muốn giao tiếp tiếng Anh tự nhiên như người bản ngữ.