WEBVTT

00:01.400 --> 00:03.520
Hello everyone and welcome.

00:04.040 --> 00:09.320
In this video, we will go over an architecture that reflects a real world agent system.

00:10.000 --> 00:17.640
The use case that we will explore here is an Excel document analyzer and the components that we would

00:17.640 --> 00:23.560
go over as Claude Desktop, which is a client interface where user and Claude interact.

00:23.880 --> 00:28.640
We have a server where the host tools and the prompt are used by Claude.

00:28.960 --> 00:35.720
We have the tools here, which are pre-built functions like extract data or generate report.

00:36.240 --> 00:41.920
Then we have prompts which are predefined templates for tasks like analyzing data.

00:42.520 --> 00:48.880
And then we have file systems where the Excel files are stored and can be accessible by the server.

00:49.320 --> 00:55.080
So let's take a step by step walk through in the entire flow of events that happen over starts, and

00:55.080 --> 01:02.560
sends a list of available capabilities like tools and prompts to the Claude Desktop client.

01:02.880 --> 01:04.120
Why does it do this?

01:04.990 --> 01:06.430
it does that.

01:06.590 --> 01:12.230
So Claude knows what it can do with the data and the tools that are available to use.

01:12.630 --> 01:18.910
Now, once the server's bootstrapped information is shared, the user makes a request to Claude and

01:18.910 --> 01:23.270
it asks it to perform an analysis of an existing Excel document.

01:23.550 --> 01:27.550
For example, summarize the data trends in this spreadsheet.

01:27.950 --> 01:36.470
So this is the first request that a user sends to the Claude LM using Claude Desktop as a host.

01:36.950 --> 01:39.950
Now Claude plans the entire task.

01:40.390 --> 01:46.350
Claude receives the user's request and examines the available tools on the server to decide how to fulfill

01:46.350 --> 01:47.430
the request.

01:47.950 --> 01:51.670
Why this matters is because Claude isn't just guessing.

01:52.030 --> 01:59.550
It uses structured tools like extract data or Generate Report to complete the task intelligently.

02:00.110 --> 02:07.430
Now coming to the third execution flow is Claude executes the tools that were explored sequentially.

02:07.430 --> 02:13.490
Eventually, Claude calls one tool at a time, feeding outputs from one step into another.

02:13.810 --> 02:22.210
So it can be the sequence of documents like first validate the document, then extract the data, then

02:22.210 --> 02:25.850
analyze the data, and then generate the report.

02:26.370 --> 02:30.290
Now the fourth step is here which is file system access.

02:30.810 --> 02:37.570
The tools on the server are granted access to necessary Excel files stored in the file system.

02:38.010 --> 02:44.090
We do this so that Claude can read and analyze the contents of this spreadsheets.

02:44.330 --> 02:51.970
It can use the data to detect trends and summarize values depending on the question that the user asked.

02:52.210 --> 02:53.690
Thank you so much.

02:54.050 --> 03:01.210
I hope you understand the overall flow of how the entire components, the communicate with each other,

03:01.210 --> 03:07.930
from the bootstrapping to performing a real time query and an MCP architecture.

03:08.250 --> 03:09.090
Thank you.

03:09.130 --> 03:11.050
I'll see you in the next video.