Shopmonkey MCP Server

list_timeclock

Retrieve technician time clock events to track clock-in/out times. Filter by user, date range, or location for staff attendance monitoring.

Instructions

List technician time clock events. Track clock-in/clock-out for shop staff.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_timeclock"
  }
}

Input Schema

Name	Required	Description
`skip`	No	Number of records to skip for pagination (default: 0)
`limit`	No	Maximum number of results to return (default: 25)
`userId`	No	Filter by user/technician ID
`endDate`	No	Filter by end date (ISO 8601 format)
`startDate`	No	Filter by start date (ISO 8601 format)
`locationId`	No	Filter by location ID. Defaults to SHOPMONKEY_LOCATION_ID env var if set.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.1Sep 8, 2026

removedInput schema / properties / page

Removed value: -{
-  "description": "Page number for pagination (default: 1)",
-  "type": "number"
-}

addedInput schema / properties / skip

Added value: +{
+  "description": "Number of records to skip for pagination (default: 0)",
+  "type": "number"
+}

First observedv1.0.0Mar 26, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description implies a read-only list operation but does not explicitly state the absence of side effects or any authorization requirements. The verb 'list' suggests non-mutating behavior, but it is not stated explicitly.

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 concise sentence that directly states the tool's function without any redundant information. It is well-structured and easy to parse.

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 simple list operation, the description is sufficient even without an explicit return format. It could mention what fields are returned, but the absence is minor given the tool's simplicity and the parameter clarity.

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 schema descriptions fully cover all six parameters (pagination, filters, location default), so the tool description adds no additional meaning beyond what is already in the input schema. This is exactly the baseline for full schema coverage.

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 clearly states the tool lists technician time clock events and tracks clock-in/clock-out for shop staff, using a specific verb ('list') and resource ('technician time clock events'). It leaves no ambiguity about the tool's purpose.

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?

The description provides no guidance on when to use this tool versus alternatives, though no direct sibling for timeclock events exists. It does not elaborate on filtering or pagination, relying instead on parameter descriptions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server