[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-mcps-new-primitives-make-agent-middleware-obsolete-zh":3,"article-related-mcps-new-primitives-make-agent-middleware-obsolete-zh":31,"series-ai-agent-cde225a8-eb8e-4724-a089-77f36af0e8a6":76},{"id":4,"slug":5,"title":6,"content":7,"summary":8,"source":9,"source_url":10,"author":11,"image_url":12,"cover_image":12,"category":13,"language":14,"translated_content":11,"related_article_id":15,"keywords":16,"key_takeaways":23,"views":27,"created_at":28,"published_at":29,"topic_cluster_id":30},"cde225a8-eb8e-4724-a089-77f36af0e8a6","mcps-new-primitives-make-agent-middleware-obsolete-zh","MCP 的新原語，正在淘汰自製 agent middleware","\u003Cp data-speakable=\"summary\">\u003Ca href=\"\u002Ftag\u002Fmcp\">MCP\u003C\u002Fa> 的 elicitation、structured output 和 prompt templates，正在取代大量自製的 \u003Ca href=\"\u002Ftag\u002Fagent\">agent\u003C\u002Fa> middleware。\u003C\u002Fp>\u003Cp>MCP 已經跨過關鍵門檻：原本團隊手工補上的 agent 行為，開始變成協議本身的一部分。MuleSoft 的 MCP Connector 更新加入 elicitation、structured output 與 prompt templates，代表系統可以直接追問缺失欄位、限制回傳格式、統一提示詞，而不必每條\u003Ca href=\"\u002Fnews\u002Fmcp-servers-ai-workflows-explained-zh\">工作流\u003C\u002Fa>都帶著脆弱的膠水\u003Ca href=\"\u002Fnews\u002Fkimi-k26-open-source-coding-agentic-ai-benchmarks-zh\">程式\u003C\u002Fa>。這不是小修小補，而是把 agent 行為從應用層搬到基礎設施層。\u003C\u002Fp>\u003Ch2>第一個論點\u003C\u002Fh2>\u003Cp>自製澄清邏輯本來就是稅，不是功能。過去一年，幾乎所有認真的 agent 工作流都得自己處理缺資料的情況：缺 region、account ID、approval flag 或日期區間時，工程師要寫分支、停下來問、驗證、再重試。這些程式碼重複、難測、也很容易在新工具或新後端接上來時壞掉。elicitation 把這段互動移進協議，因為每次工具呼叫本來就會經過協議層。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782748974384-f5w9.png\" alt=\"MCP 的新原語，正在淘汰自製 agent middleware\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>實務上的好處很直接。少了散落各服務的 one-off handler，少了藏在 orchestration code 裡的 prompt hack，也少了 agent 該問卻亂猜造成的失敗。MuleSoft 的方向很清楚：原本每個 workflow 都要自己做的 middleware，現在應該成為 protocol primitive。只要某個模式會在多個 agent 重複出現，它就該下放到應用層以下，而不是塞進每個產品團隊的自訂邏輯裡。\u003C\u002Fp>\u003Ch2>第二個論點\u003C\u002Fh2>\u003Cp>structured output 的價值，在於它把「能看」和「能用」分開。agent 失敗不只發生在缺輸入，也發生在工具回傳一大段文字，對人類看起來合理，對下一步機器操作卻毫無幫助。一般 MCP 工具回應常混有狀態敘述、metadata、協議摘要與說明文字，這對看 log 的人沒問題，對要抽一個欄位、比對一個值、或觸發下一個動作的 agent 來說卻是毒藥。structured output 讓回應變成模型能可靠消化的結構，而不是靠猜。\u003C\u002Fp>\u003Cp>這一點之所以重要，是因為 agent stack 的強度取決於最弱的交接點。輸入再乾淨，只要輸出還是雜訊，系統最後還是會退化成 prompt parsing 和 regex 補丁。structured output 拿掉了這個脆弱中介層，給 agent 一份契約，而契約才是 automation 能擴張的前提。沒有契約，團隊只是在針對某個工具的措辭做過度擬合，無法在工具與領域之間重用行為。\u003C\u002Fp>\u003Ch2>第三個論點\u003C\u002Fh2>\u003Cp>prompt templates 不是便利功能，而是治理工具。共享模板能統一 agent 怎麼提問、怎麼使用工具、怎麼處理不確定性，這會直接降低團隊之間的漂移。漂移是 agent 系統變得不可維護的最快路徑之一：每個 workflow 都發明自己的提示風格，最後組織看起來不像平台，只像一堆實驗。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782748975575-rs49.png\" alt=\"MCP 的新原語，正在淘汰自製 agent middleware\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>模板也讓審查與稽核成為可能。資安團隊可以檢查一套核准過的模式，而不是追著散落在各種 codebase 和 low-code flow 裡的提示變體跑。產品團隊也能集中調整行為，而不是在每個整合裡重複踩同樣的坑。MuleSoft 把 templates、elicitation、structured output 綁在一起是對的，因為三者本來就是同一個系統：先問對問題，再收對答案，最後保持互動一致。\u003C\u002Fp>\u003Ch2>反方可能怎麼說\u003C\u002Fh2>\u003Cp>最強的反對意見是：協議功能不會消滅複雜度，只是把它搬家。elicitation 仍然需要產品決策，像是什麼時候中斷使用者、要問多少資訊、要暴露多少上下文；structured output 仍然依賴 schema 設計，壞 schema 只會帶來另一種僵化；prompt templates 也可能變成新的中央控制層，讓每次變更都要經過平台審批，拖慢團隊。\u003C\u002Fp>\u003Cp>這個批評成立，但它沒有推翻這套原語，反而劃出邊界。協議不該取代判斷、政策或領域設計；它能取代的是每個 workflow 都重寫一次的澄清、解析與提示格式化邏輯。\u003Ca href=\"\u002Fnews\u002Fkimi-2-7-price-coding-benchmark-zh\">真正\u003C\u002Fa>該被保留在應用程式裡的，是那些確實因產品而異的決策。其他共通機械，應該標準化。\u003C\u002Fp>\u003Cp>所以答案不是拒絕 protocol primitives，而是接受它們的限制，並把重複的 middleware 從每個 app 裡抽走。不要在每個團隊裡重新造同一套輪子。把共通機制下放，才有空間讓應用程式專注在真正不同的地方。\u003C\u002Fp>\u003Ch2>你能做什麼\u003C\u002Fh2>\u003Cp>如果你是工程師，先停止為每個 agent tool 寫獨立的 retry-and-clarify 流程，改把這些行為收斂到可共享的 MCP 模式。若你是 PM，先定義 agent 什麼時候必須追問、必須回傳哪些欄位、交接格式長什麼樣，再上線下一個 workflow。若你是創辦人，把 elicitation 和 structured output 當成平台能力，而不是可有可無的附加價值，因為先標準化的人，會更快交付、更少故障，也更少陷在 agent folklore 裡 debug。\u003C\u002Fp>","我認為，MCP 的 elicitation、structured output 和 prompt templates，應該取代大部分自製 agent middleware，因為它們把重複的澄清、解析與提示治理下放成協議原語。","blogs.mulesoft.com","https:\u002F\u002Fblogs.mulesoft.com\u002Fnews\u002Fmcp-connector-updates\u002F",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782748974384-f5w9.png","ai-agent","zh","6c32d3c9-f5b9-4f47-8786-b6e8efd2660a",[17,18,19,20,21,22],"MCP","elicitation","structured output","prompt templates","agent middleware","protocol primitives",[24,25,26],"MCP 的新原語正在把重複的 agent middleware 下放到協議層。","elicitation 與 structured output 先解決澄清與交接的脆弱點。","prompt templates 的核心價值是治理，而不只是開發便利。",0,"2026-06-29T16:02:24.789168+00:00","2026-06-29T16:02:24.782+00:00","e3b68196-9e64-4c18-a3b6-a73e73bfb367",{"tags":32,"relatedLang":35,"relatedPosts":39},[33],{"name":17,"slug":34},"mcp",{"id":15,"slug":36,"title":37,"language":38},"mcps-new-primitives-make-agent-middleware-obsolete-en","MCP’s new primitives make agent middleware obsolete","en",[40,46,52,58,64,70],{"id":41,"slug":42,"title":43,"cover_image":44,"image_url":44,"created_at":45,"category":13},"6e37d84c-aa27-4d4d-bbf1-81c47dc4522d","mcp-servers-ai-workflows-explained-zh","MCP Server 讓 AI 工具接上工作流","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782747180723-q3gs.png","2026-06-29T15:32:33.536175+00:00",{"id":47,"slug":48,"title":49,"cover_image":50,"image_url":50,"created_at":51,"category":13},"a5333ae2-bfd1-434a-92dd-575e824538c3","openmontage-open-source-ai-video-production-zh","OpenMontage 證明 AI 影片製作該由開源接管","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782685072512-v02f.png","2026-06-28T22:17:22.846394+00:00",{"id":53,"slug":54,"title":55,"cover_image":56,"image_url":56,"created_at":57,"category":13},"caea04da-9e30-4eb8-bb08-2ac3afc4f09e","gemini-35-flash-computer-use-safeguards-zh","Gemini 3.5 Flash 讓你寫電腦操作腳本","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782681504454-c1ly.png","2026-06-28T21:17:56.883563+00:00",{"id":59,"slug":60,"title":61,"cover_image":62,"image_url":62,"created_at":63,"category":13},"362a448e-b40e-437c-9529-94b0fd6a7689","design-md-bridge-taste-to-ui-scaffolds-zh","DESIGN.md 是把品味變成 UI 骨架的缺失橋樑","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782586072806-w93e.png","2026-06-27T18:47:23.886521+00:00",{"id":65,"slug":66,"title":67,"cover_image":68,"image_url":68,"created_at":69,"category":13},"4a77707d-c370-4584-bf40-e71c0414720e","openclaw-agent-control-layer-matters-zh","OpenClaw 證明：代理系統的勝負在控制層，不在模型","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782561770712-4ch7.png","2026-06-27T12:02:20.114404+00:00",{"id":71,"slug":72,"title":73,"cover_image":74,"image_url":74,"created_at":75,"category":13},"d0a20a18-1c6f-40ad-b438-e10b5c48ed2e","openclaw-persistent-ai-assistant-chat-apps-zh","OpenClaw 把聊天 App 變成持久 AI","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1782559967933-o1i5.png","2026-06-27T11:32:21.569788+00:00",[77,82,87,92,97,102,107,112,117,122],{"id":78,"slug":79,"title":80,"created_at":81},"4ae1e197-1d3d-4233-8733-eafe9cb6438b","claude-now-uses-your-pc-to-finish-tasks-zh","Claude 開始幫你操作電腦","2026-03-26T07:20:48.457387+00:00",{"id":83,"slug":84,"title":85,"created_at":86},"5bede67f-e21c-413d-9ab8-54a3c3d26227","googles-2026-ai-agent-report-decoded-zh","Google 2026 AI Agent 報告解讀","2026-03-26T11:15:22.651956+00:00",{"id":88,"slug":89,"title":90,"created_at":91},"2987d097-563f-46c7-b76f-b558d8ef7c2b","kimi-k25-review-stronger-still-not-legend-zh","Kimi K2.5 評測：更強，但還不是神作","2026-03-27T07:15:55.277513+00:00",{"id":93,"slug":94,"title":95,"created_at":96},"95c9053b-e3f4-4cb5-aace-5c54f4c9e044","claude-code-controls-mac-desktop-zh","Claude Code 也能操控 Mac 了","2026-03-28T03:01:58.58121+00:00",{"id":98,"slug":99,"title":100,"created_at":101},"dc58e153-e3a8-4c06-9b96-1aa64eabbf5f","cloudflare-100x-faster-ai-agent-sandbox-zh","Cloudflare 的 AI 沙箱跑超快","2026-03-28T03:09:44.142236+00:00",{"id":103,"slug":104,"title":105,"created_at":106},"1c8afc56-253f-47a2-979f-1065ff072f2a","openai-backs-isara-agent-swarm-bet-zh","OpenAI 挺 Isara 的 agent swarm …","2026-03-28T03:15:27.513155+00:00",{"id":108,"slug":109,"title":110,"created_at":111},"7379b422-576e-45df-ad5a-d57a0d9dd467","openai-plan-automated-ai-researcher-zh","OpenAI 想做自動化 AI 研究員","2026-03-28T03:17:42.090548+00:00",{"id":113,"slug":114,"title":115,"created_at":116},"48c9889e-86df-450b-a356-e4a4b7c83c5b","harness-engineering-ai-agent-reliability-2026-zh","駕馭工程：從「馬具」到「作業系統」，AI Agent 可靠性的終極密碼","2026-03-31T06:42:53.556721+00:00",{"id":118,"slug":119,"title":120,"created_at":121},"96d8e8c8-1edd-475d-9145-b1e7a1b02b65","mcp-explained-from-prompts-to-production-zh","MCP 怎麼把提示詞變工作流","2026-04-01T09:24:39.321274+00:00",{"id":123,"slug":124,"title":125,"created_at":126},"f2ca7720-b471-4ce5-9336-2a9ac2a876fd","amazon-bedrock-agents-multi-agent-workflows-zh","Amazon Bedrock Agents 進入多代理工作流","2026-04-01T09:30:29.945429+00:00"]