Workspace369

Set team member availability

team_member_availability_set

DestructiveIdempotent

Change a team member's working availability, one day at a time, and/or the time zone those hours are in. Only the days passed change (days you omit are left as they are); clearing a day means naming it with active: false or empty slots, and an active day needs at least one slot. Times are 12-hour strings like "8:00 AM" in the member's time zone. time_zone must be an IANA zone naming a place (e.g. "America/Denver"); fixed offsets like "+05:00" or "EST" are refused. Pass days, time_zone, or both. The member is not notified. Any caller holding team.edit_permissions may edit any member, including the workspace owner, as in the app. Held until the user approves it in the Workspace369 app.

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": {
      "member_id": "<member_id>"
    },
    "name": "team_member_availability_set"
  }
}

Input Schema

Name	Required	Description
`days`	No	The days to change; days not listed are left as they are.
`member_id`	Yes	Team member id (from team_members_list).
`time_zone`	No	IANA zone naming a place (e.g. America/Denver) that the hours are in.

Output Schema

Name	Required	Description	Default
`member`	No
`approval_id`	No
`approval_url`	No
`held_for_approval`	No
`approval_expires_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026
- changedInput schema / properties / member_id / description
```
Previous value: -"Team member id."New value: +"Team member id (from team_members_list)."
```
First observedOct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that only the passed days change, that the member is not notified, that any caller holding `team.edit_permissions` can edit any member including the workspace owner, that the change is held until user approval in the Workspace369 app, and the IANA-only time zone rule. These are exactly the mutation/permission/reversibility facts an agent needs and that destructiveHint/idempotentHint alone 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-loads the core action and keeps every sentence factual and load-bearing, with no filler. Slightly dense and mildly redundant in places (e.g. the partial-update rule is stated in both the opening line and the later 'only the days passed change' clause), but overall efficient.

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?

Covers partial-edit semantics, clearing behavior, validation constraints, permission model, notification behavior, and the approval workflow; an output schema exists so return values need not be described. Nothing material is missing for correct invocation.

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 rules not encoded in the schema, notably that an active day requires at least one slot and that fixed offsets like '+05:00' or 'EST' are refused. These raise the value above the schema baseline.

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 a team member's working availability ... and/or the time zone') and scopes it to one day at a time, which cleanly separates it from the read sibling team_member_availability_get. An agent can identify the operation without opening 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 Guidelines4/5

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

Gives clear operational context: pass `days`, `time_zone`, or both; omitted days are untouched; clearing uses `active: false` or empty `slots`; an active day needs at least one slot. It does not explicitly name the read counterpart (team_member_availability_get) as the alternative for inspecting availability, so routing guidance is strong but not complete.

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

All Workspace369 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.