Outcome
By the end of this lesson, you will be able to complete one real task end to end through an assistant, recognise the moment it stops being a demo, and decide what you will hand it next.
| Tier | Engineer |
| JTBD | ”Stop testing the connection and actually use it.” |
| Personas | Platform Engineer · SRE · FinOps Analyst |
| Prerequisites | M6.2.L4 |
| Time | 9 minutes |
| Bloom verb | Complete (Apply), Recognise (Understand), Decide (Evaluate) |
1. Concept
Verification tells you the wiring works. It does not tell you anything you wanted to know. This lesson is the first question you ask because you actually need the answer.
The shape of a real task, as opposed to a demo:
A DEMO has a known answer, and you check the answerA REAL TASK has an unknown answer, and you act on itThat difference is why this lesson asks you to pick the question rather than handing you one.
Three that are worth the first attempt
1. "What is our biggest avoidable cost right now, and what would fixing it involve?" crosses recommendations, resources and cost in one answer
2. "Which of our non-production resources are running outside working hours, and what would a schedule save?" the exact question this whole curriculum is built around
3. "What changed in our estate this week, and who changed it?" the question a console answers in five tabsEach is a read. None needs write access, and each produces something you can take to somebody else.
The moment it stops being a demo
You will notice it: the answer contains something you did not know, and your next sentence is about what to do rather than about whether it worked. That is the point of the tool, and it usually arrives on the second or third question rather than the first.
2. Demo
YOU "Which non-production resources ran outside working hours last week, and what would scheduling them save?"
ASSISTANT 47 resources across 2 accounts ~312 idle hours estimated saving if scheduled 19:00 to 08:00: $1,840 a month the three largest: two RDS instances and a GPU node group
YOU "Show me the GPU one. Who owns it?"The second sentence is the tell. Nobody asks that of a demo.
3. Hands-on (6 min)
1. Pick one of the three questions above, or write your own. It must be a question you do not already know the answer to.2. Ask it. Read the answer properly rather than skimming for whether it worked.3. Ask one follow-up that narrows it: a team, an account, a single resource.4. Write down one thing you learned that you would not have gone looking for in the console.5. Decide what you will ask next week, and put it somewhere you will see it.Ask for it instead. The task you would have done in the console, asked in one sentence.
BEFORE An account on the product you connected in L1 to L3, with a cloud connected and discovery finished.ASK "Which non-production resources ran outside working hours last week, and what would scheduling them save?"CHECK whether you believe the number. If you do not, ask what it was calculated from, because a figure you cannot defend is worse than no figure.Tools behind it: list_resources (read, Explore), get_recommendations (read, Optimize), get_cost_by_resources (read, Cost), get_schedule_success (read, Cost). The full catalogue is at zop.dev/learn/mcp-tools.
4. Knowledge check
Q1
What separates a real first task from a verification step?
A. Its answer is unknown to you, and you act on it
B. It uses a write tool
C. It takes longer
D. It crosses two products
Show answer
Correct: A. Verification checks the wiring against an answer you already have. A real task produces something you did not know, which is the only kind of answer worth changing a decision over. Writes and product boundaries are incidental.
Q2
You get a saving estimate you find hard to believe. The right next move:
A. Ignore it
B. Act on it immediately
C. Ask what it was calculated from
D. Re-run the query
Show answer
Correct: C. A number you cannot defend is worse than no number, because somebody will eventually ask. Asking for the basis is one more sentence and it is what makes the figure usable in a meeting.
Q3
Why do the three suggested first tasks all use reads?
A. Writes are disabled by default
B. Because reads are faster
C. Because write tools require a PAT
D. Because each produces something you can act on without needing permission to change anything yet
Show answer
Correct: D. A first task should not depend on your organisation’s write posture. Reads are available at every level, so the exercise works on day one regardless of what an admin has enabled.
5. Apply
Put one recurring question in your week. Monday morning, one sentence, whatever matters most to your team: what changed, what is idle, what is about to breach a budget.
KEEP the first answer that told you something you did not know the follow-up question you asked after itThe second one is the better artefact. It is evidence that you stopped testing the tool and started using it.
Related lessons
Glossary terms touched
MCP · MCP configuration · MCP native · PAT