Skip to main content
Glama

update_my_availability

Update when the coach is bookable for sessions (confirm-gated). This is the same availability that drives trainerAvailableHourSlotsNext7Days / session booking. Working hours can be split: pass timeRanges, e.g. [{start:'05:00',end:'09:00'},{start:'18:00',end:'22:00'}] — slots are only offered inside them. checkIn/checkOut is the older single-window form.

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": {
      "preferredTime": "<preferredTime>",
      "daysAvailable": "<daysAvailable>",
      "timezone": "<timezone>"
    },
    "name": "update_my_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkInNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
checkOutNo
timezoneYes
timeRangesNo
daysAvailableYes
preferredTimeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, non-open-world write. The description adds genuinely useful behavior: execution is gated behind confirm=true with a preview fallback, and the change propagates to trainerAvailableHourSlotsNext7Days and session booking. It does not say what happens to already-booked sessions when hours are narrowed.

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?

The opening sentence establishes purpose and the confirm gate up front, and the remainder is tight, with the inline JSON example doing real work. Only the downstream identifier string is mildly noisy but it is informative.

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 7-parameter mutation with no output schema and only 14% schema coverage, the description covers the confirm gate, the propagation effect, and the two competing time-window forms, which is the core of calling it correctly. The gap is the unexplained required fields preferredTime and daysAvailable.

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?

Schema description coverage is 14%, so the description carries most of the burden, and it does explain timeRanges with a concrete two-window example plus the legacy checkIn/checkOut pairing. However the required parameters preferredTime and daysAvailable are never explained (format, allowed day names, or meaning), leaving critical semantics undocumented.

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 gives a specific verb and resource ('Update when the coach is bookable for sessions') and ties it to its downstream effect on slot offering and session booking. It is clearly distinct from sibling update_my_* tools for unrelated profile fields, though it doesn't name any alternative tool explicitly.

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?

It states the confirm gate ('Must be true to actually execute... otherwise returns a preview only') and signals that checkIn/checkOut is the 'older single-window form', which steers the agent toward timeRanges. There is no explicit when-to-use/when-not guidance relative to other booking-related tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.