<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Model Context Protocol on Prasham H Trivedi</title><link>https://prashamhtrivedi.in/tags/model-context-protocol/</link><description>Recent content in Model Context Protocol on Prasham H Trivedi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 13 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://prashamhtrivedi.in/tags/model-context-protocol/index.xml" rel="self" type="application/rss+xml"/><item><title>Tools vs Resources vs Prompts: the MCP primitive you're misusing</title><link>https://prashamhtrivedi.in/mcp-primitive-youre-misusing/</link><pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate><guid>https://prashamhtrivedi.in/mcp-primitive-youre-misusing/</guid><description>MCP has three primitives, not one. Most servers cram everything into Tools, then blame the protocol for bloated context. The fix is one question per call: who pulls the trigger, the model, the app, or the user. Get it wrong on read-only data and you have handed the model a decision it should never have been making, and you cannot see the bad ones on a token counter.</description></item></channel></rss>