Skip to main content
Glama
pashaydev

Terminal.shop MCP Server

by pashaydev

delete-card

Remove a payment card from your Terminal.shop account to manage payment methods and update billing information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardIdYes

Implementation Reference

  • The main handler function for the 'delete-card' tool. It takes a cardId, calls terminalApi.delete to remove the card, and returns a success or error response in the expected MCP format.
    async ({ cardId }) => {
      try {
        await terminalApi.delete(`/card/${cardId}`);
        return {
          content: [
            {
              type: "text",
              text: `Card deleted successfully`,
            },
          ],
        };
      } catch (error) {
        console.error(`Error deleting card ${cardId}:`, error);
        return {
          content: [
            {
              type: "text",
              text: `Error deleting card: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    },
  • The input schema for the 'delete-card' tool, defining the required 'cardId' parameter as a string using Zod.
    {
      cardId: z.string(),
    },
  • server.js:994-1024 (registration)
    The registration of the 'delete-card' tool using server.tool(), specifying the name, input schema, and handler function.
    // Tool to delete a card
    server.tool(
      "delete-card",
      {
        cardId: z.string(),
      },
      async ({ cardId }) => {
        try {
          await terminalApi.delete(`/card/${cardId}`);
          return {
            content: [
              {
                type: "text",
                text: `Card deleted successfully`,
              },
            ],
          };
        } catch (error) {
          console.error(`Error deleting card ${cardId}:`, error);
          return {
            content: [
              {
                type: "text",
                text: `Error deleting card: ${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