Skip to main content
Glama
pashaydev

Terminal.shop MCP Server

by pashaydev

create-token

Generate authentication tokens for AI assistants to access Terminal.shop's API, enabling product browsing, cart management, order placement, and subscription handling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline handler for the "create-token" tool, registered directly in the server.tool call. It creates a personal access token by sending a POST request to the "/token" endpoint using the terminalApi client, returns a formatted success message containing the token ID and token value, and handles errors appropriately.
    // Tool to create a personal access token
    server.tool("create-token", {}, async () => {
      try {
        const response = await terminalApi.post("/token");
        const data = response.data.data;
    
        return {
          content: [
            {
              type: "text",
              text: `Token created successfully!\n\nToken ID: ${data.id}\nToken: ${data.token}\n\nIMPORTANT: Save this token securely. You won't be able to see the full token value again.`,
            },
          ],
        };
      } catch (error) {
        console.error("Error creating token:", error);
        return {
          content: [
            {
              type: "text",
              text: `Error creating token: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    });
  • server.js:1105-1105 (registration)
    Registers the "create-token" tool on the MCP server with an empty input schema (no parameters required). The handler is defined inline.
    server.tool("create-token", {}, async () => {
  • Empty input schema for the create-token tool, indicating no input parameters are required.
    server.tool("create-token", {}, async () => {
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