Skip to main content
Glama
baskcart

W3Ship MCP Server

by baskcart

list_bookings

Retrieve confirmed session bookings with optional filters for location or date to manage scheduling and availability.

Instructions

List all confirmed session bookings. Optionally filter by location or date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationIdNoFilter by location ID
dateNoFilter by date (YYYY-MM-DD)

Implementation Reference

  • The handler for the 'list_bookings' tool which fetches booking information from the W3Ship API.
    case 'list_bookings': {
        const locationId = args?.locationId as string | undefined;
        const date = args?.date as string | undefined;
    
        const params = new URLSearchParams();
        if (locationId) params.set('locationId', locationId);
        if (date) params.set('date', date);
        const queryStr = params.toString() ? `?${params.toString()}` : '';
    
        const bookingsRes = await fetch(`${W3SHIP_API}/api/bookings${queryStr}`);
        const bookingsData = await bookingsRes.json();
    
        return { content: [{ type: 'text', text: JSON.stringify(bookingsData, null, 2) }] };
    }
  • src/index.ts:194-203 (registration)
    The tool registration block for 'list_bookings' in the server configuration.
        name: 'list_bookings',
        description: 'List all confirmed session bookings. Optionally filter by location or date.',
        inputSchema: {
            type: 'object',
            properties: {
                locationId: { type: 'string', description: 'Filter by location ID' },
                date: { type: 'string', description: 'Filter by date (YYYY-MM-DD)' },
            },
        },
    },
Behavior2/5

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

No annotations provided, so description carries full burden. Mentions 'confirmed' state but doesn't explain booking lifecycle states, pagination behavior, or what happens when filters match nothing. Omits auth/permission requirements.

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?

Two efficient sentences with zero waste. Front-loaded with primary action, followed by filtering capabilities.

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

Completeness3/5

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

Adequate for a simple 2-parameter list operation without output schema, but lacks domain context (what defines a 'session' vs other bookable entities) and return value expectations.

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?

Schema coverage is 100% with clear descriptions. The description confirms filters are optional ('Optionally'), matching the zero required parameters, but adds no syntax guidance beyond the schema's YYYY-MM-DD hint.

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

Purpose4/5

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

Clear verb ('List') and resource ('confirmed session bookings'), with 'confirmed' usefully distinguishing from sibling 'get_available_slots'. However, it doesn't clarify relationship to 'hold_slot' or 'get_order' which may represent similar concepts in this domain.

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

Usage Guidelines2/5

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

No guidance on when to use versus siblings like 'hold_slot' (which likely precedes booking) or 'get_order'. No mention of prerequisites or filter selection strategy.

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