SimpleDock

This connector has been deprecated

Duplicate listing. This is the same server as SimpleDock (ai.simpledock/simple-dock) (https://simpledock.ai/api/v1/mcp). Please use that listing instead.

Book appointment

create_appointment

Book a confirmed appointment (staff bookings skip the approval queue). startTime must be one get_availability offers for that type and date; any other time is rejected with conflict. Inactive appointment types can't be booked (not_found). Answer each required field from list_appointment_types. Emails the carrier a confirmation at contactEmail. Returns the new appointment. Requires scope appointments:write (Scheduler role or above).

Input Schema

Name	Required	Description
`notes`	No	Notes from the carrier or scheduler, visible to staff.
`doorId`	No	Specific door to use. Only honored when the location assigns doors; omit to auto-pick.
`poNumbers`	No	Every purchase order on this appointment, in order. Duplicates ignoring case are dropped. When set, this wins over poReference.
`startTime`	Yes	A startTime returned by get_availability, unchanged.
`driverName`	No	Driver's name.
`locationId`	Yes	Location id, from list_locations.
`companyName`	Yes	Carrier company name.
`contactName`	No	Carrier contact person's name.
`driverNotes`	No	Instructions for the driver.
`driverPhone`	No	Driver's mobile; check-in texts go here when SMS check-in is on.
`poReference`	No	One purchase order. Kept for older clients. Prefer poNumbers when the load has more than one. If both are sent, poNumbers wins. Sending only this replaces the list with this single value.
`contactEmail`	Yes	Carrier contact email; confirmations and changes are emailed here.
`contactPhone`	No	Carrier contact phone, e.g. +1 214 555 0100.
`customFields`	No	Answers to the type's booking questions, keyed by fieldDefinitions[].key, e.g. { "sealNumber": "A123" }. A MULTI_TEXT question takes an array of strings, e.g. { "customerPo": ["4501", "4502"] }.
`trailerNumber`	No	Trailer number.
`appointmentTypeId`	Yes	Appointment type id, from list_appointment_types (get_location_setup also lists inactive types).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 22, 2026
- addedInput schema / properties / companyName / maxLength
```
Added value: +200
```
- addedInput schema / properties / contactName / maxLength
```
Added value: +120
```
- addedInput schema / properties / contactPhone / maxLength
```
Added value: +40
```

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / customFields / description

Previous value: -"Answers to the type's booking questions, keyed by fieldDefinitions[].key, e.g. { \"sealNumber\": \"A123\" }."New value: +"Answers to the type's booking questions, keyed by fieldDefinitions[].key, e.g. { \"sealNumber\": \"A123\" }. A MULTI_TEXT question takes an array of strings, e.g. { \"customerPo\": [\"4501\", \"4502\"] }."

Changed2 schema fields changedOct 22, 2026

addedInput schema / properties / poNumbers

Added value: +{
+  "description": "Every purchase order on this appointment, in order. Duplicates ignoring case are dropped. When set, this wins over poReference.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / poReference / description

Previous value: -"Purchase order or load reference number."New value: +"One purchase order. Kept for older clients. Prefer poNumbers when the load has more than one. If both are sent, poNumbers wins. Sending only this replaces the list with this single value."

Changed1 schema field changedOct 16, 2026

addedInput schema / properties / contactName

Added value: +{
+  "description": "Carrier contact person's name.",
+  "type": "string"
+}

Changed14 schema fields changedOct 16, 2026

addedInput schema / properties / appointmentTypeId / description

Added value: +"Appointment type id, from list_appointment_types (get_location_setup also lists inactive types)."

addedInput schema / properties / companyName / description
```
Added value: +"Carrier company name."
```

addedInput schema / properties / contactEmail / description

Added value: +"Carrier contact email; confirmations and changes are emailed here."

addedInput schema / properties / contactPhone / description

Added value: +"Carrier contact phone, e.g. +1 214 555 0100."

addedInput schema / properties / customFields / description

Added value: +"Answers to the type's booking questions, keyed by fieldDefinitions[].key, e.g. { \"sealNumber\": \"A123\" }."

addedInput schema / properties / doorId / description

Added value: +"Specific door to use. Only honored when the location assigns doors; omit to auto-pick."

addedInput schema / properties / driverName / description
```
Added value: +"Driver's name."
```
addedInput schema / properties / driverNotes / description
```
Added value: +"Instructions for the driver."
```

addedInput schema / properties / driverPhone / description

Added value: +"Driver's mobile; check-in texts go here when SMS check-in is on."

addedInput schema / properties / locationId / description
```
Added value: +"Location id, from list_locations."
```

addedInput schema / properties / notes / description

Added value: +"Notes from the carrier or scheduler, visible to staff."

addedInput schema / properties / poReference / description

Added value: +"Purchase order or load reference number."

changedInput schema / properties / startTime / description

Previous value: -"ISO 8601 datetime"New value: +"A startTime returned by get_availability, unchanged."

addedInput schema / properties / trailerNumber / description
```
Added value: +"Trailer number."
```

First observedOct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses side effects (emails the carrier a confirmation at contactEmail), validation behavior (non-offered startTime is rejected with conflict; inactive type returns not_found), the approval-queue bypass, return behavior, and required scope/role. This is substantially richer than the structured hints alone.

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 dense but front-loaded: purpose first, then constraints, validation failures, side effects, return behavior, and auth. Every sentence contributes operational information, with no filler.

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

Completeness5/5

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

For a 16-parameter mutation with nested customFields and no output schema, the description covers the critical workflow, error cases, side effects, permissions, and the fact that the new appointment is returned. Optional parameter details are already fully documented in the schema, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds useful cross-tool provenance for two critical parameters: startTime must be an unchanged value from get_availability, and required fields should come from list_appointment_types. It does not explain every optional parameter, but it meaningfully improves the two that most affect successful invocation.

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 starts with a specific verb and resource ('Book a confirmed appointment') and immediately distinguishes the staff-booking path from the approval queue. An agent can tell this apart from siblings like approve_appointment or reschedule_appointment without reading the schema.

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

Usage Guidelines5/5

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

It gives explicit preconditions: startTime must come from get_availability for that type and date, required fields must be answered from list_appointment_types, and inactive types cannot be booked. It also explains that staff bookings skip approval, which is exactly the when/when-not context an agent needs.

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

All SimpleDock tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?