<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>API Design on AI VOID</title><link>https://ai-blog.noorshomelab.dev/categories/api-design/</link><description>Recent content in API Design on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 24 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/categories/api-design/index.xml" rel="self" type="application/rss+xml"/><item><title>The Problem &amp;amp; The Promise of MCP: Why Dynamic Context Matters</title><link>https://ai-blog.noorshomelab.dev/mastering-mcp/mcp-problem-promise/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mastering-mcp/mcp-problem-promise/</guid><description>&lt;p&gt;Imagine an intelligent assistant or an AI agent that needs to help you write code, debug a system, or analyze a complex business process. For it to be truly effective, it can&amp;rsquo;t just operate in a vacuum. It needs to understand &lt;em&gt;your&lt;/em&gt; specific project, &lt;em&gt;your&lt;/em&gt; unique setup, and the dynamic state of &lt;em&gt;your&lt;/em&gt; systems. This is where traditional tools often fall short, leaving a critical gap: the &lt;strong&gt;context problem&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id="why-this-chapter-matters"&gt;Why This Chapter Matters&lt;/h2&gt;
&lt;p&gt;In an increasingly AI-driven world, the ability for intelligent tools to understand their environment is paramount. Without proper context, an AI is like a brilliant but blind expert – full of knowledge, but unable to apply it effectively to your specific situation. This chapter lays the foundational understanding for why the Model Context Protocol (MCP) exists. You&amp;rsquo;ll grasp the core problem of context delivery to intelligent systems and how MCP provides a robust, standardized solution, setting the stage for building truly smart and adaptable applications.&lt;/p&gt;</description></item><item><title>Crafting Tool Schemas: Declaring Capabilities and UI Resources</title><link>https://ai-blog.noorshomelab.dev/mcp-ai-tool-integration-guide/tool-schemas-and-ui-resources/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mcp-ai-tool-integration-guide/tool-schemas-and-ui-resources/</guid><description>&lt;h2 id="introduction-giving-your-ai-agent-a-blueprint"&gt;Introduction: Giving Your AI Agent a Blueprint&lt;/h2&gt;
&lt;p&gt;Welcome back, future AI architects! In our previous chapter, we explored the foundational concepts of the Model Context Protocol (MCP) and understood its role as a universal language for AI agents to interact with the world. Now, let&amp;rsquo;s dive into the heart of MCP: &lt;strong&gt;tool schemas&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Imagine you&amp;rsquo;re training a personal assistant. You wouldn&amp;rsquo;t just tell it, &amp;ldquo;Go order food.&amp;rdquo; You&amp;rsquo;d give it a clear, step-by-step guide: &amp;ldquo;To order food, you need to know the restaurant, the items, and the delivery address.&amp;rdquo; This guide is essentially a schema. For AI agents, tool schemas are the precise, machine-readable blueprints that define &lt;em&gt;what&lt;/em&gt; a tool can do, &lt;em&gt;how&lt;/em&gt; to use it, and even &lt;em&gt;how&lt;/em&gt; to visually represent its interactions.&lt;/p&gt;</description></item></channel></rss>