Opens in a new tab
Skip to main content
Lesson 05 of 10

Discover What This Session Can Actually Do

Check the relevant tools and source available to the current session before promising connected work.

About 10 minutesNo coding experience neededExplore in your browser

Look around. Try a small click.

This lesson works as a written guide with interactive examples. You can explore here before opening the real application or provider dashboard. A recorded video has not been added yet.

Read the short lesson

What will make more sense

  • Check the relevant tools and source available to the current session before promising connected work.
  • Current session availability and source identity establish what the assistant can use now.
  • The assistant must distinguish supported capability from an unavailable action.

One idea to keep

Check the relevant tools and source available to the current session before promising connected work.

The short lesson

Read the explanation at your pace

Having a connection saved somewhere does not prove its tools are available in the conversation you are using now. Applications can organize capabilities by session, workspace, selected agent, enabled tools or account policy. Before asking for connected work, find out what the current session can actually access. This is a practical check, not a programming task.

The prepared session-card.md lists three fictional capabilities: search approved booking notes, read one booking and prepare a local summary. It does not offer cancellation, payment collection or sending messages. The assistant should work from that list rather than inventing an action because the user mentioned it. If a needed capability is missing, it can explain the limitation and suggest a supported next step.

MCP servers describe the tools they expose, including information about the inputs those tools accept. A compatible application can discover those offerings. What reaches the assistant can also depend on account permissions and application settings. The simple question is, “Which relevant tools are available here, and what do they do?” You do not need to inspect a technical schema to understand the answer.

In VS Code, the way you manage tools or connections can depend on the selected agent harness and version. The current documented route can start from Chat, Open Customizations, MCP Servers, Add Server. Select the intended harness and follow its supported setup. Review the source and authentication prompts before accepting anything. Our optional action only inspects the area; it does not require adding a server. Start with the capabilities required for the work you actually chose.

An assistant should also identify whether a claimed source is live, cached, downloaded or simply a prepared example. Our lesson's booking record is an example, so its answer cannot establish today's real schedule. In actual business work, ask for the source and timing that matter. A connected name on a menu is less useful than an understandable lookup result from the intended account.

Choose the activity response that checks current capabilities before promising a booking update. You can still make progress when a tool is absent by preparing a draft or asking for the missing information. The useful habit is to keep the session's real abilities visible and to describe the outcome accurately, rather than treating every saved integration as active and authorized everywhere.

Try it here

Try it here · no installation needed

Choose the next small step

Follow the prepared example, then select a response to see why it fits. Nothing is connected or changed.

This is a local learning example with prepared responses. It does not run VS Code or contact an AI service.

STEP 1Identify the selected session and account
STEP 2Inspect the relevant offered capabilities
STEP 3Match the request to what is actually available

A connector was configured last month. What should you check now?

A prompt you can keep

These are example words to copy into your own AI chat when you want to try them. Copying does not send a request.

Read the prepared example for this lesson. Explain the proposed action, its target and the expected result. Keep this as an explanation; do not change files or connect accounts.

A tiny next step, if you want one

Optional: try 2 small actions at your own pace

You can finish this lesson by exploring the example above. These real-app actions are optional, and there is nothing to submit.

  1. Optional: read session-card.md.
  2. Optional: locate your assistant’s tools or connections area and inspect the listed capabilities without enabling extras.

A quick confidence check

These checkmarks are a personal reminder. Choose what feels familiar, and come back whenever you want.

Your place is saved in this browser when storage is available. There is no grading or account sync.

Try a short question

Choose an answer to see why it fits. You can try again or explore every explanation.

A connector was configured last month. What should you check now?

The offered tools can read bookings but not cancel them. Can the agent claim a cancellation?

If something looks different

My assistant or VS Code uses a different label.

Use the official help for your selected assistant and version. The course teaches the decision; the exact menu or capability can differ.

I do not have the account or feature used in the example.

Use the prepared browser example and downloaded notes. No account connection or paid service is required to complete this course.

Sources and further help

Read the official product guidance and related learning resources when you need them. You do not need to read every reference now.