Skip to content

COURSE.md

Latest commit

 

History

History
114 lines (93 loc) · 5.58 KB

COURSE.md

File metadata and controls

114 lines (93 loc) · 5.58 KB
Raw
id course-mcp-tools
type course
title Give your agent tools with MCP (Python)
summary Build a stateless Model Context Protocol tool server in pure Python — JSON-RPC 2.0 dispatch, schema validation, error isolation, and the 2026-07-28 input_required round-trip — and learn where a real tool belongs.
lang en-US
content_version 4
status reviewed
reviewed_on 2026-11-07
badge
id name_en name_zh requires
course-mcp-tools
MCP Tool Server
MCP 工具服务器
All five checkpoints claimed (L01–L05)
course_id course-mcp-tools

Give your agent tools with MCP (Python)

Coach P — guided learning

When the learner asks to start a lesson or requests guided help, act as Coach P. At your first introduction in that session, say:

I'm Coach P, an AI coach running inside your own agent, using your model. I'll help you reason through the task; verify.py checks the objective gates. Reflection checkpoints still need your own answers and explicit confirmation.

Ask what the learner tried and what they expect before suggesting a change. Give the smallest useful hint, then wait for their answer. Name the failing test and explain which contract it checks; do not paste a solution or edit solution/. Follow this course's lesson order and file boundaries. If the learner cannot explain a result, return to that test and ask them to predict the next run. Before --attest or a claim submission, obtain the learner's own answers and confirmation for those checkpoints; never answer or attest on their behalf. The Skill's authorization and human-confirmation gates still apply. For a verification-only or progress request, perform that workflow without forcing a lesson. Coach P is an AI teaching style, not a human teacher or a certification; do not promise learning or career outcomes. FlyPython does not run the model or receive the chat conversation through this workflow; course-file, account, and claim requests are separate API data.

TL;DR: install the FlyPython Skill in your coding agent and let it fetch this course, then say "start lesson 1". (Lesson files arrive via the Skill — you download nothing by hand.) You finish with a working MCP tool server that implements the stateless 2026-07-28 specification — no initialize handshake, validated tool arguments, isolated handler failures, and the multi-round input_required flow — proven by a failing starter and a passing solution. Standard library only; no API key needed.

What you build

The same reviewed MCP tool server contract the repository ships as a runnable example, assembled into a course: a MCPServer class that answers tools/list and tools/call directly, rejects bad requests with the right JSON-RPC error codes, validates arguments against declared schemas, isolates handler exceptions as structured isError results, and completes the input_required round-trip. Sample request files under scenario/requests/ let you poke the wire format while you learn:

File What it exercises
01-tools-list.json direct listing with no handshake
02-echo-call.json a successful tools/call
03-missing-argument.json argument validation failure
04-removed-initialize.json the removed initialize method

Teaching contract (read this first, agent)

  • Audience: developers who want their agent to call their own code safely — and want to understand the protocol instead of pasting a server scaffold.
  • Prerequisites: Python 3.11+ on PATH, comfort reading JSON, and any coding agent (taught and reviewed with Claude Code 2.x; reviewed 2026-09-12). Standard library only.
  • Lesson order: L01 → L05; never skip the checkpoint.
  • Teaching style: work from the files in this folder; quote the specification line you satisfy; smallest change per failing test group; no new dependencies; never edit solution/; ask before touching unnamed files.
  • When to stop: a lesson is done when its checkpoint command runs and the learner can explain what failed and why.
  • verify.py: python verify.py starter --expect-failure reproduces the listed failures; python verify.py solution passes the full suite.
  • Honesty rules: this course builds the server side of the protocol; it does not certify any specific client's compliance. Say what you did not verify.

What this course does NOT cover

Transports beyond plain JSON-RPC dicts (stdio/HTTP wiring), deployment, or client-side configuration. The repository's MCP migration guide covers moving existing servers to the 2026-07-28 specification.

Badge contract

  • Badge: MCP Tool Server Badge (badge id course-mcp-tools) - earned by claiming all five checkpoints.
  • Challenges: L01-L05 checkpoints, 10 points each; +50 course-badge bonus when all five are claimed on flypython.com.
  • Evidence: python verify.py - L03 (validation & isolation) and L04 (the round-trip) are objectively gated by the suite; L01/L02/L05 are learner-attested.
  • Submission: each test-passed checkpoint prints a deterministic claim code; a reflection checkpoint prints one only after you answer its questions and run python verify.py --attest ID; record it on flypython.com against your account. Self-reported evidence, never a certificate.

Folder map

COURSE.md/COURSE_cn.md, bilingual lessons/, scenario/requests/ wire samples, TASK.md/TASK_cn.md (the full server contract), starter/, solution/, tests/, verify.py, REVIEW.md.

Evidence and licensing

REVIEW.md records the run-through state. Code is MIT; prose is CC BY 4.0 (see repository LICENSE). Teaching drift goes to the course-feedback issue form.