Pratica di Shadowing: MCP Just Got a Whole Lot Better - Impara a parlare inglese con i video
Scegli una modalità di pratica
Ogni modalità apre una sala di pratica a schermo intero.
61 frasi
Se le frasi sono troppo corte o troppo lunghe, clicca su Edit per modificarle.
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.
Scarica l'app
Tutto ciò che serve per parlare fluentemente
Pronuncia con IAVoto per ogni frase
Pratica IPAPadroneggia ogni suono
VocabolarioCostruisci il tuo lessico
Gioco di vocabolarioImpara giocando
FOR YOU
Video consigliato
C11
143 frasi
MCP vs API: The protocol every developer needs to know
Business EnglishUniversity StudentsWorking Adults
C11
309 frasi
Claude Code: The Advanced Guide (99% of Devs Skip These Features)
Business EnglishUniversity StudentsWorking Adults
C112
25 frasi
Introducing the Agents API
Business EnglishUniversity StudentsWorking Adults
C13
51 frasi
Business Partner C1. Unit 1. Video 1.1.1.
Business EnglishUniversity StudentsWorking Adults
C1117 frasi
I've Changed My Opinion On DEVELOPERS Vibe Coding
Business EnglishUniversity StudentsWorking Adults
C16
49 frasi
What Are Microservices Really All About? (And When Not To Use It)
Business EnglishUniversity StudentsWorking Adults
C14
78 frasi
Connect Slack to Salesforce with Hosted MCP Servers | Salesforce Headless 360 Decoded
Business EnglishUniversity StudentsWorking Adults
C11
197 frasi
Unreal Engine 5.8 - Experimental MCP Server Support Walkthrough | State of Unreal 2026
Business EnglishWorking Adults
C12
151 frasi
Wrote My Own Memory Allocator (and ran DOOM with It)
Business EnglishUniversity StudentsWorking Adults
C12
339 frasi
Easy Migration from Postgres to Databricks Lakebase
Business EnglishUniversity StudentsWorking Adults
C14
58 frasi
The mystery is solved... and the answer is 40x cheaper than Claude
American AccentBusiness EnglishUniversity StudentsWorking Adults
C13
200 frasi
CAP Theorem in System Design Interviews
Business EnglishInterview EnglishUniversity Students
Vocabolario e note di pronuncia per questa lezione
Questa lezione di conversazione di livello C1 si basa sul video “MCP Just Got a Whole Lot Better”. Le parole che ritornano più spesso: tool, Mcp, agent, Api, server. Questo video contiene 61 frasi e 1064 parole da ripetere con lo shadowing. Il parlato dura 5:55. Chi parla va veloce, circa 180 parole al minuto: aspettati suoni legati e ridotti. Solo il 81% delle parole rientra nelle 3.000 più comuni dell’inglese, quindi il lessico è impegnativo.
Vocaboli chiave di questo video
Le 15 parole più avanzate del video, con pronuncia e significato:
| Parola | Pronuncia | Significato |
|---|---|---|
| endpoint sostantivo | estremo | |
| neon sostantivo | /ˈniˌɑn/ | neon, neo |
| ergonomic aggettivo | ergonomico | |
| workflow sostantivo | /ˈwɝkfloʊ/ | flusso di lavoro, procedura |
| compute verbo | /kəmˈpjuːt/ | computare, elaborare |
| sandbox sostantivo | /ˈsæn(d).bɑks/ | sabbionaia, sabbiera |
| token sostantivo | /ˈtoʊkən/ | simbolo, segno |
| bundle sostantivo | /ˈbʌn.dl̩/ | insieme, fascina |
| execute verbo | /ˈɛksɪˌkjuːt/ | giustiziare |
| expose verbo | /ɪkˈspoʊz/ | esporre, evidenziare |
| exponentially avverbio | /ɛkspə(ʊ)ˈnɛnʃəli/ | esponenzialmente |
| shortcut sostantivo | /ˈʃɔːtkʌt/ | scorciatoia, sentiero tagliato |
| inspect verbo | /ɪnˈspɛkt/ | ispezionare, investigare |
| attach verbo | /əˈtæt͡ʃ/ | legare, appiccare |
| straightforward aggettivo | /ˌstɹeɪtˈfɔː(ɹ)wə(ɹ)d/ | facile, semplice |
I phrasal verb che sentirai
| Parola | Pronuncia | Significato |
|---|---|---|
| blow up verbo | saltare in aria, esplodere | |
| check out verbo | investigare | |
| end up verbo | andare a finire, finire | |
| figure out verbo | scoprire, rendersi conto | |
| go ahead verbo | /ˌɡoʊ əˈhɛd/ | procedere, andare avanti |
| slow down verbo | rallentare, decelerare | |
| take over verbo | usurpare | |
| turn out verbo | risultare |
Pronuncia a cui fare attenzione
Chi parla usa 5 contrazioni e forme ridotte, come I'll, isn't, we're. Pronunciale nella forma breve, così come le senti.
- I suoni “sh” e “zh”: exponentially /ɛkspə(ʊ)ˈnɛnʃəli/, shortcut /ˈʃɔːtkʌt/, speculation /ˌspɛk.jəˈleɪ.ʃən/, accomplish /əˈkɑm.plɪʃ/, traditionally /tɹəˈdɪʃ.ə.nə.li/
- Parole lunghe — attenzione all’accento: 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/
I suoni difficili per chi parla italiano:
- Consonante finale — senza aggiungere una vocale dopo: compute /kəmˈpjuːt/, sandbox /ˈsæn(d).bɑks/, execute /ˈɛksɪˌkjuːt/, expose /ɪkˈspoʊz/, programmatic /ˌpɹəʊ.ɡɹəˈmæt.ɪk/
- /æ/ — più aperta della “e”: sandbox /ˈsæn(d).bɑks/, adapter /əˈdæptəɹ/, programmatic /ˌpɹəʊ.ɡɹəˈmæt.ɪk/, attach /əˈtæt͡ʃ/, interact /ɪn.təˈɹækt/
Come esercitarsi con questo video
- Ascolta tutto il video una volta senza parlare e annota le parole che non conosci.
- Inizia a velocità 0,75×, fai shadowing frase per frase e torna alla velocità normale quando diventa facile.
- Registrati e confronta con l’originale, facendo attenzione a parole come endpoint, neon, ergonomic.
Cos'è la tecnica dello Shadowing?
Shadowing è una tecnica di apprendimento delle lingue supportata da studi scientifici, originariamente sviluppata per la formazione dei traduttori professionisti e resa popolare dal poliglotta Dr. Alexander Arguelles. Il metodo è semplice ma potente: ascolti un audio in inglese di madrelingua e lo ripeti immediatamente ad alta voce — come un'ombra che segue il parlante con un ritardo di solo 1–2 secondi. A differenza dell'ascolto passivo o degli esercizi di grammatica, lo shadowing costringe il tuo cervello e i muscoli della bocca a elaborare e riprodurre simultaneamente i modelli di discorso reale. La ricerca dimostra che migliora significativamente la precisione della pronuncia, l'intonazione, il ritmo, il discorso connesso, la comprensione dell'ascolto e la fluidità del parlato — rendendolo uno dei metodi più efficaci per la preparazione alla prova di speaking dell'IELTS e per la comunicazione reale in inglese.