Skip to main content
Glama
wspotter

MCP Art Supply Store

by wspotter

get_employee_schedule

Retrieve employee shift schedules and availability for effective staff planning and management at the art supply store.

Instructions

Get employee schedule and shift information for staffing planning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format or day of week

Implementation Reference

  • Handler implementation for the 'get_employee_schedule' tool. It returns the list of employees with their roles, shifts, and hourly rates from the mock storeData, ignoring the date parameter.
    case 'get_employee_schedule': {
      const date = String(args?.date || new Date().toLocaleDateString('en-US', { weekday: 'long' }));
      
      return {
        content: [{
          type: 'text',
          text: `šŸ‘„ Employee Schedule:\n\n${storeData.employees.map(emp =>
            `${emp.name} - ${emp.role}\nšŸ“… ${emp.shift}\nšŸ’µ Rate: $${emp.hourlyRate}/hr`
          ).join('\n\n')}`
        }]
      };
    }
  • Tool schema definition including name, description, and input schema for the date parameter.
    {
      name: 'get_employee_schedule',
      description: 'Get employee schedule and shift information for staffing planning.',
      inputSchema: {
        type: 'object',
        properties: {
          date: { type: 'string', description: 'Date in YYYY-MM-DD format or day of week' },
        },
      },
    },
  • Mock employee data used by the get_employee_schedule handler.
    employees: [
      { id: 'EMP001', name: 'Alex Johnson', role: 'Store Manager', shift: 'Mon-Fri 9AM-6PM', hourlyRate: 22 },
      { id: 'EMP002', name: 'Maria Santos', role: 'Sales Associate', shift: 'Tue-Sat 10AM-7PM', hourlyRate: 16 },
      { id: 'EMP003', name: 'David Kim', role: 'Art Specialist', shift: 'Wed-Sun 11AM-8PM', hourlyRate: 18 },
    ]
  • src/index.ts:516-518 (registration)
    Registration of the ListToolsRequestHandler which exposes the tools list including get_employee_schedule.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • src/dashboard.ts:60-60 (registration)
    Tool listed in dashboard mock data for UI display.
    { name: 'get_employee_schedule', description: 'Staff schedules', category: 'Operations' },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get' implying a read operation, but doesn't disclose behavioral traits like whether it returns all employees or filtered results, pagination, authentication needs, rate limits, or error conditions. This is inadequate for a tool with no annotation coverage.

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 with zero waste. It front-loads the core purpose ('Get employee schedule and shift information') and adds brief context ('for staffing planning'), making it appropriately sized and well-structured.

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?

Given no annotations, no output schema, and a single parameter with full schema coverage, the description is incomplete. It lacks details on return values (e.g., format, scope), behavioral constraints, or error handling, which are critical for a tool with no structured data to compensate.

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, documenting the 'date' parameter as 'Date in YYYY-MM-DD format or day of week'. The description adds no additional parameter semantics beyond this, so it meets the baseline of 3 where 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 verb 'Get' and the resource 'employee schedule and shift information', with the purpose 'for staffing planning' providing context. It distinguishes from most siblings (e.g., sales or inventory tools), but doesn't explicitly differentiate from similar scheduling tools like 'check_appointments' or 'book_appointment'.

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 explicit guidance on when to use this tool versus alternatives is provided. The description mentions 'staffing planning' as context, but doesn't specify prerequisites, exclusions, or compare to other tools like 'check_appointments' or 'get_daily_sales' for related needs.

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