Skip to main content
Glama
pashaydev

Terminal.shop MCP Server

by pashaydev

create-subscription

Set up recurring product deliveries by specifying variant, quantity, shipping address, payment method, and frequency schedule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productVariantIDYes
quantityYes
addressIDYes
cardIDYes
scheduleYes

Implementation Reference

  • The handler function that implements the core logic for creating a subscription by making a POST request to the terminalApi /subscription endpoint with the provided parameters.
    async ({ productVariantID, quantity, addressID, cardID, schedule }) => {
      try {
        const response = await terminalApi.post("/subscription", {
          productVariantID,
          quantity,
          addressID,
          cardID,
          schedule,
        });
    
        return {
          content: [
            {
              type: "text",
              text: `Subscription created successfully!`,
            },
          ],
        };
      } catch (error) {
        console.error("Error creating subscription:", error);
        return {
          content: [
            {
              type: "text",
              text: `Error creating subscription: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    },
  • Zod schema defining the input parameters for the create-subscription tool: productVariantID (string), quantity (positive integer), addressID (string), cardID (string), and schedule object.
    {
      productVariantID: z.string(),
      quantity: z.number().int().positive(),
      addressID: z.string(),
      cardID: z.string(),
      schedule: z.object({
        type: z.enum(["fixed", "weekly"]),
        interval: z.number().int().positive().optional(),
      }),
    },
  • server.js:1027-1070 (registration)
    The server.tool call that registers the 'create-subscription' tool, including its name, input schema, and inline handler function.
    server.tool(
      "create-subscription",
      {
        productVariantID: z.string(),
        quantity: z.number().int().positive(),
        addressID: z.string(),
        cardID: z.string(),
        schedule: z.object({
          type: z.enum(["fixed", "weekly"]),
          interval: z.number().int().positive().optional(),
        }),
      },
      async ({ productVariantID, quantity, addressID, cardID, schedule }) => {
        try {
          const response = await terminalApi.post("/subscription", {
            productVariantID,
            quantity,
            addressID,
            cardID,
            schedule,
          });
    
          return {
            content: [
              {
                type: "text",
                text: `Subscription created successfully!`,
              },
            ],
          };
        } catch (error) {
          console.error("Error creating subscription:", error);
          return {
            content: [
              {
                type: "text",
                text: `Error creating subscription: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      },
    );
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