Skip to main content
Glama
wspotter

MCP Art Supply Store

by wspotter

check_appointments

View scheduled appointments for specific dates or customers to manage your art supply store's calendar and customer bookings.

Instructions

Check scheduled appointments for a specific date or customer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format (default: today)

Implementation Reference

  • Tool schema definition including name, description, and input schema for the check_appointments tool. Part of the tools array returned by ListToolsRequestHandler.
      name: 'check_appointments',
      description: 'Check scheduled appointments for a specific date or customer.',
      inputSchema: {
        type: 'object',
        properties: {
          date: { type: 'string', description: 'Date in YYYY-MM-DD format (default: today)' },
        },
      },
    },
  • Handler implementation for check_appointments tool. Filters mock appointments data by date and returns formatted text response.
    case 'check_appointments': {
      const date = String(args?.date || new Date().toISOString().split('T')[0]);
      const appointments = storeData.appointments.filter(a => a.date === date);
      
      return {
        content: [{
          type: 'text',
          text: appointments.length > 0
            ? `šŸ“… Appointments for ${date}:\n\n${appointments.map(apt =>
                `ā° ${apt.time} - ${apt.service}\nšŸ‘¤ Customer: ${apt.customerName}\nā±ļø Duration: ${apt.duration}`
              ).join('\n\n')}`
            : `No appointments scheduled for ${date}`
        }]
      };
  • Mock appointments data used by the check_appointments handler.
    appointments: [
      { id: 'APT001', customerName: 'Sarah Martinez', service: 'Custom Framing Consultation', date: '2025-10-05', time: '14:00', duration: '30 min' },
      { id: 'APT002', customerName: 'Lisa Park', service: 'Art Technique Workshop', date: '2025-10-06', time: '10:00', duration: '2 hours' },
    ],
  • src/index.ts:516-518 (registration)
    Registration of all tools list including check_appointments via ListToolsRequestHandler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • src/dashboard.ts:58-58 (registration)
    Mock tool registration in the dashboard server for UI display.
    { name: 'check_appointments', description: 'View appointments', category: 'Operations' },
Behavior2/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 states the tool 'checks' appointments, implying a read-only operation, but doesn't clarify permissions, rate limits, output format, or whether it returns all appointments or filtered results. This leaves significant gaps for a tool that likely queries sensitive data.

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 description is a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action, resource, and scope concisely.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and potential complexity in handling appointments (e.g., privacy, filtering), the description is inadequate. It doesn't explain return values, error conditions, or behavioral nuances, leaving the agent under-informed about how to interpret results.

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, with the 'date' parameter fully documented in the schema itself. The description adds no additional parameter semantics beyond implying a 'customer' parameter that isn't in the schema, creating confusion rather than value. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

The description clearly states the tool's purpose with a specific verb ('check') and resource ('scheduled appointments'), and specifies the scope ('for a specific date or customer'). However, it doesn't explicitly differentiate from sibling tools like 'get_employee_schedule' or 'book_appointment', which prevents a perfect score.

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?

The description provides minimal guidance by mentioning 'for a specific date or customer', but offers no explicit advice on when to use this tool versus alternatives like 'get_employee_schedule' or 'lookup_customer'. There's no mention of prerequisites, exclusions, or recommended contexts, leaving usage ambiguous.

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/wspotter/mcpart'

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