lesgooo.fun

Set availability

set_availability

DestructiveIdempotent

Changes one participant's availability: all-day dates and/or exact free-time windows (ISO start and end with offset, plus the IANA time_zone). mode=add merges, remove subtracts, replace overwrites. Use when the user says which days or hours they are or are no longer free. It does not set the agreed Event date or an RSVP.

Input Schema

Name	Required	Description
`mode`	No	add/remove change supplied days/windows; replace is a full replacement when time_slots is supplied. Default replace (legacy all-day behavior).
`plan`	Yes	Saved plan link (e.g. https://lesgooo.fun/ab12/when) or its 4-character plan ID. Links without a plan ID (e.g. https://lesgooo.fun/when) are unsaved local drafts and are not accepted.
`dates`	Yes
`time_zone`	No	The user's IANA time zone, e.g. Europe/Prague.
`time_slots`	No	Optional exact windows. For hours-only changes pass dates=[] and mode=add/remove; replace changes the entire availability. End is exclusive.
`participant_id`	Yes	From create_plan or join_plan.
`participant_token`	Yes	From create_plan or join_plan.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

changedInput schema / properties / plan / description

Previous value: -"Saved plan link (e.g. https://lesgooo.fun/ab12/when) or its 4-character id. Bare module links such as https://lesgooo.fun/when are local drafts: ask for a saved link, never substitute a previous plan ID."New value: +"Saved plan link (e.g. https://lesgooo.fun/ab12/when) or its 4-character plan ID. Links without a plan ID (e.g. https://lesgooo.fun/when) are unsaved local drafts and are not accepted."

changedInput schema / properties / time_zone / description

Previous value: -"Known IANA zone such as Europe/Prague; required for time_slots and edits to existing exact windows. Ask if unknown."New value: +"The user's IANA time zone, e.g. Europe/Prague."

Changed3 schema fields changedOct 23, 2026

changedInput schema / properties / mode / description

Previous value: -"replace sets the entire list; add and remove change only the supplied dates. Default: replace."New value: +"add/remove change supplied days/windows; replace is a full replacement when time_slots is supplied. Default replace (legacy all-day behavior)."

addedInput schema / properties / time_slots

Added value: +{
+  "description": "Optional exact windows. For hours-only changes pass dates=[] and mode=add/remove; replace changes the entire availability. End is exclusive.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "end": {
+        "description": "ISO timestamp with Z or UTC offset, after start, max 7 days.",
+        "type": "string"
+      },
+      "start": {
+        "description": "ISO timestamp with Z or UTC offset.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "start",
+      "end"
+    ],
+    "type": "object"
+  },
+  "maxItems": 300,
+  "type": "array"
+}

addedInput schema / properties / time_zone

Added value: +{
+  "description": "Known IANA zone such as Europe/Prague; required for time_slots and edits to existing exact windows. Ask if unknown.",
+  "type": "string"
+}

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / mode / description

Added value: +"replace sets the entire list; add and remove change only the supplied dates. Default: replace."

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / plan / description

Previous value: -"Plan link (e.g. https://lesgooo.fun/ab12/when) or its 4-character id."New value: +"Saved plan link (e.g. https://lesgooo.fun/ab12/when) or its 4-character id. Bare module links such as https://lesgooo.fun/when are local drafts: ask for a saved link, never substitute a previous plan ID."

First observedSep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already flag destructive=true and idempotent=true, so the description's real contribution is the mode semantics: add merges, remove subtracts, replace overwrites. That tells the agent which calls can wipe prior availability, which is the key risk context. It stops short of saying replace discards all existing windows and entries.

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?

Three sentences, front-loaded with what changes, then mode semantics, then when to use it and what it is not. Every clause carries distinct information with no repetition of the title.

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 destructive mutation with no output schema, this covers payload shape, mode behavior, use trigger, and sibling exclusions; the schema already documents formats, limits, and credential sources. An agent can invoke it correctly from this definition plus the schema.

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 description coverage is already 86%, so the baseline is a 3; the description earns the extra point by tying parameters together into one model (all-day dates plus exact windows that must be ISO with offset and a matching IANA time_zone). The mode definitions largely restate what the schema's mode enum description already says.

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 (changes) and resource (one participant's availability) with the exact payload shape: all-day dates and/or ISO free-time windows plus IANA time zone. It explicitly excludes the two most confusable siblings, the agreed Event date (update_event) and RSVP (set_rsvp), so an agent can route 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?

"Use when the user says which days or hours they are or are no longer free" is a clear positive trigger, and "It does not set the agreed Event date or an RSVP" names the nearest competing actions. It does not spell out prerequisites (a saved plan plus participant_id/token), though the schema requires them.

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

All lesgooo.fun tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?