Skip to main content
Glama
yoshiko-pg

o3-search MCP

by yoshiko-pg

o3-search

Perform web searches using natural language queries to find current information, troubleshoot errors, or discuss complex problems.

Instructions

An AI agent with advanced web search capabilities. Useful for finding the latest information, troubleshooting errors, and discussing ideas or design challenges. Supports natural language queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesAsk questions, search for information, or consult about complex problems in English.

Implementation Reference

  • index.ts:47-83 (handler)
    The handler function that executes the o3-search tool logic. It takes an input string, calls OpenAI's responses.create with web_search_preview tool and reasoning effort, then returns the output text.
      async ({ input }) => {
        try {
          const response = await openai.responses.create({
            model: config.model,
            input,
            tools: [
              {
                type: "web_search_preview",
                search_context_size: config.searchContextSize,
              },
            ],
            tool_choice: "auto",
            parallel_tool_calls: true,
            reasoning: { effort: config.reasoningEffort },
          });
    
          return {
            content: [
              {
                type: "text",
                text: response.output_text || "No response text available.",
              },
            ],
          };
        } catch (error) {
          console.error("Error calling OpenAI API:", error);
          return {
            content: [
              {
                type: "text",
                text: `Error: ${error instanceof Error ? error.message : "Unknown error occurred"}`,
              },
            ],
          };
        }
      },
    );
  • Input schema for the o3-search tool using Zod: a single required string input describing the user's query.
    {
      input: z
        .string()
        .describe(
          "Ask questions, search for information, or consult about complex problems in English.",
        ),
    },
  • index.ts:37-83 (registration)
    Registration of the 'o3-search' tool on the McpServer instance, including its name, description, input schema, and handler.
    server.tool(
      "o3-search",
      `An AI agent with advanced web search capabilities. Useful for finding the latest information, troubleshooting errors, and discussing ideas or design challenges. Supports natural language queries.`,
      {
        input: z
          .string()
          .describe(
            "Ask questions, search for information, or consult about complex problems in English.",
          ),
      },
      async ({ input }) => {
        try {
          const response = await openai.responses.create({
            model: config.model,
            input,
            tools: [
              {
                type: "web_search_preview",
                search_context_size: config.searchContextSize,
              },
            ],
            tool_choice: "auto",
            parallel_tool_calls: true,
            reasoning: { effort: config.reasoningEffort },
          });
    
          return {
            content: [
              {
                type: "text",
                text: response.output_text || "No response text available.",
              },
            ],
          };
        } catch (error) {
          console.error("Error calling OpenAI API:", error);
          return {
            content: [
              {
                type: "text",
                text: `Error: ${error instanceof Error ? error.message : "Unknown error occurred"}`,
              },
            ],
          };
        }
      },
    );
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description bears full burden. It mentions 'advanced web search capabilities' and 'supports natural language queries', but it does not disclose limitations, return format, or error handling. This is adequate but not rich in behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler. The first sentence states the primary function, and the second provides usage context. Every sentence is valuable and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and no output schema, the description covers purpose, use cases, and input language specification. It could mention output format or limitations, but it is sufficiently complete for an LLM to understand the tool's role.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with one parameter. The description adds that queries should be in English and can include complex problems, which slightly enhances the schema's param description. However, since coverage is high, the baseline is 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'AI agent with advanced web search capabilities', providing a specific verb (search) and resource (web). It also lists use cases like finding latest information, troubleshooting errors, and discussing ideas, which clarifies its purpose without needing sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'useful for finding the latest information, troubleshooting errors, and discussing ideas or design challenges', giving clear context on when to use the tool. No siblings exist, so no exclusion guidance is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yoshiko-pg/o3-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server