Skip to main content
Glama
pashaydev

Terminal.shop MCP Server

by pashaydev

search-products

Find products in Terminal.shop by entering search queries to browse available items through the MCP server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo

Implementation Reference

  • server.js:430-499 (registration)
    Registration of the 'search-products' tool using McpServer.tool() method, including inline schema and handler function.
    server.tool(
      "search-products",
      {
        query: z.string().optional(),
      },
      async ({ query = "" }) => {
        try {
          const response = await terminalApi.get("/product");
          const products = response.data.data;
    
          // Filter products if query is provided
          const filteredProducts = query
            ? products.filter(
                (p) =>
                  p.name.toLowerCase().includes(query.toLowerCase()) ||
                  p.description.toLowerCase().includes(query.toLowerCase()),
              )
            : products;
    
          if (filteredProducts.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: `No products found matching "${query}".`,
                },
              ],
            };
          }
    
          // Format the response
          let formattedText = query
            ? `# Products matching "${query}"\n\n`
            : "# All Terminal.shop Products\n\n";
    
          filteredProducts.forEach((product) => {
            formattedText += `## ${product.name}\n`;
            formattedText += `ID: ${product.id}\n`;
            formattedText += `${product.description}\n\n`;
    
            formattedText += "### Variants:\n";
            product.variants.forEach((variant) => {
              formattedText += `- ${variant.name}: $${variant.price / 100} (ID: ${variant.id})\n`;
            });
    
            formattedText += "\n";
          });
    
          return {
            content: [
              {
                type: "text",
                text: formattedText,
              },
            ],
          };
        } catch (error) {
          console.error("Error searching products:", error);
          return {
            content: [
              {
                type: "text",
                text: `Error searching products: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      },
    );
  • The handler function fetches all products from the Terminal.shop API, optionally filters them by the provided query in name or description, formats the matching products with their details and variants as markdown text, and returns it in the MCP content format. Handles errors gracefully.
    async ({ query = "" }) => {
      try {
        const response = await terminalApi.get("/product");
        const products = response.data.data;
    
        // Filter products if query is provided
        const filteredProducts = query
          ? products.filter(
              (p) =>
                p.name.toLowerCase().includes(query.toLowerCase()) ||
                p.description.toLowerCase().includes(query.toLowerCase()),
            )
          : products;
    
        if (filteredProducts.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: `No products found matching "${query}".`,
              },
            ],
          };
        }
    
        // Format the response
        let formattedText = query
          ? `# Products matching "${query}"\n\n`
          : "# All Terminal.shop Products\n\n";
    
        filteredProducts.forEach((product) => {
          formattedText += `## ${product.name}\n`;
          formattedText += `ID: ${product.id}\n`;
          formattedText += `${product.description}\n\n`;
    
          formattedText += "### Variants:\n";
          product.variants.forEach((variant) => {
            formattedText += `- ${variant.name}: $${variant.price / 100} (ID: ${variant.id})\n`;
          });
    
          formattedText += "\n";
        });
    
        return {
          content: [
            {
              type: "text",
              text: formattedText,
            },
          ],
        };
      } catch (error) {
        console.error("Error searching products:", error);
        return {
          content: [
            {
              type: "text",
              text: `Error searching products: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    },
  • Zod input schema defining an optional 'query' string parameter for filtering products.
    {
      query: z.string().optional(),
    },
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/pashaydev/terminal.shop.mcp'

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