Skip to main content
Glama
Sign In

Fresha MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Add blocked time

add_blocked_time
Destructive

Block a time slot in a team member's calendar so nobody books it. Adds blocked time as Add > Blocked time in the calendar does: one block on one day for one team member at one location (default: their primary location), with a title and a note for the team. It does not repeat. Clients cannot book it online unless allow_online_booking is true. Nobody is told.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_member_id": "<team_member_id>",
      "start_at": "<start_at>",
      "end_at": "<end_at>"
    },
    "name": "add_blocked_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoReason shown on the calendar, e.g. Lunch.
end_atYesEnd on the same day. ISO 8601 like start_at.
start_atYesStart, ISO 8601: 2026-11-03T14:30 is wall clock in the business's time zone; with an offset (2026-11-03T14:30:00+01:00) it is converted.
descriptionNoNote your team sees on the block.
location_idNoLocation whose calendar gets the block, one where the team member works. Default: the team member's primary location.
team_member_idYesTeam member id from list_team_members.
allow_online_bookingNoClients may still book this time online. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / location_id
      Added value: +{
+  "description": "Location whose calendar gets the block, one where the team member works. Default: the team member's primary location.",
+  "pattern": "^[0-9]+$",
+  "type": "string"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true; the description adds genuinely non-obvious behavior: no notifications are sent ('Nobody is told'), the block does not repeat, and online booking is blocked by default unless allow_online_booking is true. It does not explain how a block is later removed or whether the operation is reversible, which is the one behavioral gap.

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 what it does and scoped tightly; every sentence carries information. The 'as Add > Blocked time in the calendar does' analogy is slightly UI-dependent but helps anchor behavior for a reader familiar with the product.

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?

With 7 parameters, no output schema, and annotations covering safety, the description supplies the essential behavioral context (non-recurrence, notification silence, booking gating, location default). It is complete enough to call correctly, though it omits any mention of reversal or what the response contains.

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. The description still adds value by framing title/note as team-visible and confirming location defaults to the member's primary location and that allow_online_booking gates online booking.

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 ('Block a time slot in a team member's calendar') and pins the scope precisely: one block, one day, one team member, one location, non-repeating. An agent can distinguish this from create_appointment or find_available_slots without opening either schema.

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?

Gives clear context ('so nobody books it', 'not repeat', 'clients cannot book unless allow_online_booking is true'), which implies when to use it versus booking an appointment. It does not explicitly name an alternative sibling (e.g., create_appointment for actual bookings), so it stops short of full when/when-not routing.

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

All Fresha MCP Server and API by Cotlet 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