Skip to main content
Glama
Sign In

SimpleDock

by ai.simpledock
OverviewDiscussionsAdmin
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.

Update notification settings

update_notification_settings
DestructiveIdempotent

Change who hears about bookings at a location. notifyEmail is one extra address that gets booking alerts besides the team (empty string clears it). emailNotificationsEnabled turns carrier confirmation emails on or off; smsCheckInEnabled texts drivers a check-in link before their appointment. detailsReminderDays (1, 2, 3, 5, 7; 0 turns it off) is how many days before a recurring appointment the booker is emailed for load details still missing; detailsFinalReminder adds a last nudge 24 hours before. Omitted fields are left unchanged. Returns the location's notification settings. Requires scope locations:write (Admin role).

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation id, from list_locations.
notifyEmailNoExtra alert address, e.g. dock@acme.com. "" clears it.
smsCheckInEnabledNoText drivers a check-in link before arrival.
detailsReminderDaysNoDays before a recurring appointment to ask the booker for missing load details. 0 = off.
detailsFinalReminderNoAlso remind 24 hours before if details are still missing.
emailNotificationsEnabledNoCarrier confirmation and change emails on/off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / detailsFinalReminder
      Added value: +{
+  "description": "Also remind 24 hours before if details are still missing.",
+  "type": "boolean"
+}
    • addedInput schema / properties / detailsReminderDays
      Added value: +{
+  "description": "Days before a recurring appointment to ask the booker for missing load details. 0 = off.",
+  "enum": [
+    0,
+    1,
+    2,
+    3,
+    5,
+    7
+  ],
+  "type": "integer"
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / emailNotificationsEnabled / description
      Added value: +"Carrier confirmation and change emails on/off."
    • addedInput schema / properties / locationId / description
      Added value: +"Location id, from list_locations."
    • addedInput schema / properties / notifyEmail / description
      Added value: +"Extra alert address, e.g. dock@acme.com. \"\" clears it."
    • addedInput schema / properties / smsCheckInEnabled / description
      Added value: +"Text drivers a check-in link before arrival."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond annotations: discloses partial-update semantics, the auth scope and role required, that it returns the location's settings, and the real-world side effects (texting drivers, emailing bookers, carrier confirmations). This is substantive context the destructiveHint/idempotentHint annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then field semantics sentence-by-sentence. Dense and slightly run-on, but nearly every clause carries information an agent needs, so it earns its length.

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 6-parameter mutation tool with no output schema, the description covers what changes, partial-update behavior, permissions, and the return value. Nothing essential for correct invocation 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 baseline is 3, but the description adds genuine meaning: 0 turns detailsReminderDays off, the final reminder fires 24 hours before, and empty string clears notifyEmail. Adds value beyond the schema's per-field descriptions.

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?

States a specific verb and resource: 'Change who hears about bookings at a location', and enumerates the exact settings it governs. An agent can distinguish it from update_location_settings by the notification-specific field list.

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

Usage Guidelines4/5

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

Explicitly states that omitted fields are left unchanged and that an empty string clears notifyEmail, plus the required scope (locations:write, Admin role). It doesn't name a sibling alternative for location-level vs notification-level settings, but the context is otherwise clear.

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

All SimpleDock toolsInspect
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