<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Tool Call on KnightLi Blog</title>
        <link>https://knightli.com/en/tags/tool-call/</link>
        <description>Recent content in Tool Call on KnightLi Blog</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en</language>
        <lastBuildDate>Sat, 06 Jun 2026 22:26:00 +0800</lastBuildDate><atom:link href="https://knightli.com/en/tags/tool-call/index.xml" rel="self" type="application/rss+xml" /><item>
        <title>Is the OpenAI Plugins repository still worth looking at? Understanding the evolution of tool calls from the plug-in era</title>
        <link>https://knightli.com/en/2026/06/06/openai-plugins-archive-guide/</link>
        <pubDate>Sat, 06 Jun 2026 22:26:00 +0800</pubDate>
        
        <guid>https://knightli.com/en/2026/06/06/openai-plugins-archive-guide/</guid>
        <description>&lt;p&gt;&lt;code&gt;openai/plugins&lt;/code&gt; is a sample repository related to early OpenAI Plugins. Although today&amp;rsquo;s OpenAI tool system has evolved into function calling, tools, Agents SDK, MCP, etc., this warehouse still has reference value: it can help understand how the matter of &amp;ldquo;letting the model call external tools&amp;rdquo; was first commercialized.&lt;/p&gt;
&lt;p&gt;To today&amp;rsquo;s developers, it looks more like historical data and design samples than a go-to template for new projects.&lt;/p&gt;
&lt;h2 id=&#34;why-is-it-still-worth-watching&#34;&gt;Why is it still worth watching?
&lt;/h2&gt;&lt;p&gt;The core issues of AI tool invocation have not changed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How does the model know which tools are available;&lt;/li&gt;
&lt;li&gt;How to describe tool capabilities;&lt;/li&gt;
&lt;li&gt;How to declare parameters;&lt;/li&gt;
&lt;li&gt;How the results are returned;&lt;/li&gt;
&lt;li&gt;How to handle permissions and user confirmation;&lt;/li&gt;
&lt;li&gt;How third-party services can be safely called by models.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In the Plugins era, manifest, OpenAPI schema, server-side API and other methods are used to solve these problems. Later function calling, tool calling, and MCP are still evolving around these issues in essence.&lt;/p&gt;
&lt;h2 id=&#34;suitable-for-whom-to-watch&#34;&gt;Suitable for whom to watch
&lt;/h2&gt;&lt;p&gt;This warehouse is suitable for:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;People who want to understand the historical design of OpenAI Plugins;&lt;/li&gt;
&lt;li&gt;People working on AI tool ecosystem or Agent platform;&lt;/li&gt;
&lt;li&gt;People who need to understand manifest / OpenAPI tool description;&lt;/li&gt;
&lt;li&gt;People who want to compare the differences between Plugins, function calling, and MCP;&lt;/li&gt;
&lt;li&gt;People who maintain old plugins or migrate old solutions.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you are a new project, it is not recommended to directly copy the old Plugins model. Priority should be given to the current official API, tools, Apps SDK or MCP related documents.&lt;/p&gt;
&lt;h2 id=&#34;what-can-be-learned-from-this&#34;&gt;What can be learned from this?
&lt;/h2&gt;&lt;p&gt;The most valuable thing to learn is not a certain piece of code, but the tool interface design idea:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The tool description must be understandable by the model;&lt;/li&gt;
&lt;li&gt;API schema should be clear enough;&lt;/li&gt;
&lt;li&gt;The returned results must be suitable for the model to continue reasoning;&lt;/li&gt;
&lt;li&gt;User authorization cannot be hidden in a black box;&lt;/li&gt;
&lt;li&gt;Have understandable error messages when external tools fail.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These principles are still valid today.&lt;/p&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;&lt;code&gt;openai/plugins&lt;/code&gt; is more like slicing in the early stages of an AI tool call. It is not necessarily suitable for direct use in new projects, but it is very suitable for understanding how the line of &amp;ldquo;plug-ins, tools, and agent capability expansion&amp;rdquo; develops.&lt;/p&gt;
&lt;p&gt;If you are currently integrating AI Agent tools, reading it can help you see the source of many design problems.&lt;/p&gt;
&lt;h2 id=&#34;reference-sources&#34;&gt;Reference sources
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;&lt;a class=&#34;link&#34; href=&#34;https://github.com/openai/plugins&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;
    &gt;openai/plugins - GitHub&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
        </item>
        
    </channel>
</rss>
