Skip to main content
Glama
baskcart

W3Ship MCP Server

by baskcart

hold_slot

Reserve a bookable service time slot for 10 minutes while payment is processed. Use this tool to temporarily hold appointments by providing slot and cart IDs.

Instructions

Hold/reserve a session time slot for a customer. The slot is held for 10 minutes pending payment. Works for any bookable service.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotIdYesThe time slot ID to hold
cartIdYesThe cart ID to associate with the hold
participantsNoNumber of participants (default: 1)

Implementation Reference

  • Handler for the 'hold_slot' tool, which sends a POST request to the W3Ship API to reserve a time slot.
    case 'hold_slot': {
        const slotId = args?.slotId as string;
        const cartId = args?.cartId as string;
        const participants = (args?.participants as number) || 1;
    
        if (!slotId || !cartId) {
            return { content: [{ type: 'text', text: 'Error: slotId and cartId are required.' }], isError: true };
        }
    
        const holdRes = await fetch(`${W3SHIP_API}/api/slots`, {
            method: 'POST',
            headers: { 'Content-Type': 'application/json' },
            body: JSON.stringify({ slotId, cartId, participants }),
        });
        const holdData = await holdRes.json();
    
        return { content: [{ type: 'text', text: JSON.stringify(holdData, null, 2) }] };
    }
  • Registration and input schema definition for the 'hold_slot' tool.
        name: 'hold_slot',
        description: 'Hold/reserve a session time slot for a customer. The slot is held for 10 minutes pending payment. Works for any bookable service.',
        inputSchema: {
            type: 'object',
            properties: {
                slotId: { type: 'string', description: 'The time slot ID to hold' },
                cartId: { type: 'string', description: 'The cart ID to associate with the hold' },
                participants: { type: 'number', description: 'Number of participants (default: 1)' },
            },
            required: ['slotId', 'cartId'],
        },
    },
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully communicates the critical 10-minute expiry window and the pending payment state, but omits other important behavioral details such as failure modes, idempotency, or what happens when the hold expires.

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?

The three-sentence structure is optimally front-loaded: action definition first, critical constraint (10 minutes) second, scope clarification third. Every sentence conveys essential information with zero redundancy or filler text.

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?

Given the absence of both output schema and annotations, the description adequately compensates by explaining the operational effect (temporary hold). However, it could be improved by describing the return value or success/failure indicators expected from this mutation operation.

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?

The input schema has 100% description coverage, establishing a baseline of 3. The description implies the relationship between parameters ('pending payment' hints at cartId's purpose), but does not add syntax details, validation rules, or format constraints beyond what the schema already provides.

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 provides specific verbs (hold/reserve), identifies the exact resource (session time slot), and clarifies the beneficiary (customer). The phrase 'Works for any bookable service' effectively scopes the tool's applicability and distinguishes it from potentially service-specific booking tools.

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 provides clear temporal context ('held for 10 minutes pending payment') that implies the tool's position in a checkout workflow. However, it stops short of explicitly naming sibling alternatives like confirm_payment or stating exclusion conditions (e.g., 'do not use if slot already held').

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/baskcart/w3ship-mcp-server'

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