Skip to main content
Glama
baskcart

W3Ship MCP Server

by baskcart

get_available_slots

Find available time slots for booking services at a specific location and date, displaying times, capacity, pricing, and activity types.

Instructions

Get available session time slots for a location on a given date. Returns times, capacity, pricing, and activity type. Works for any bookable service (VR, fitness, dining, salon, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationIdYesLocation ID (e.g. loc_downtown, loc_mall)
dateYesDate in YYYY-MM-DD format
activityIdNoOptional activity/service ID to filter slots

Implementation Reference

  • Implementation of the get_available_slots tool handler, which forwards the request to the W3Ship API.
    case 'get_available_slots': {
        const locationId = args?.locationId as string;
        const date = args?.date as string;
        const activityId = (args?.activityId || args?.gameId) as string | undefined;
    
        if (!locationId || !date) {
            return { content: [{ type: 'text', text: 'Error: locationId and date are required.' }], isError: true };
        }
    
        // Map activityId to gameId for the W3Ship API
        const slotsUrl = `${W3SHIP_API}/api/slots?locationId=${locationId}&date=${date}${activityId ? `&gameId=${activityId}` : ''}`;
        const slotsRes = await fetch(slotsUrl);
        const slotsData = await slotsRes.json();
    
        return { content: [{ type: 'text', text: JSON.stringify(slotsData, null, 2) }] };
    }
Behavior3/5

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

No annotations provided, so description carries full burden. Compensates well by disclosing return values (times, capacity, pricing, activity type) absent an output schema. However, missing operational details like whether data is real-time vs cached, rate limits, or timezone handling.

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?

Three sentences, zero waste: sentence 1 states purpose, sentence 2 discloses return structure, sentence 3 defines applicable domains. Front-loaded with action verb. No redundant 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?

For a 3-parameter query tool with no output schema, description adequately compensates by listing return fields and service domains. Would benefit from mentioning pagination (if many slots) or error cases (invalid dates), but covers core functionality well.

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?

Input schema has 100% description coverage (locationId with examples, date format specified, activityId noted as optional). Description references 'location' and 'date' but adds no semantic details beyond the schema documentation. Baseline 3 appropriate since schema is self-sufficient.

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?

Excellent specificity with verb 'Get' + resource 'available session time slots' + scope 'for a location on a given date'. The examples of bookable services (VR, fitness, dining, salon) clearly distinguish this from sibling action tools like hold_slot, create_order, and list_bookings.

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

Usage Guidelines3/5

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

Provides domain context by listing applicable service types (VR, fitness, dining, salon), implying this is a pre-booking availability check. However, lacks explicit guidance on workflow transition to hold_slot for reserving or create_order for purchasing, and doesn't state prerequisites.

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