Skip to main content
Glama

update_schedule

Idempotent

Update a calendar schedule by modifying its title, description, duration, interval, availability, time zone, or moving it to another calendar.

Instructions

Update a calendar schedule. Supports owner, title, description, duration, interval, availability, timeZone, and calendar move by calendarId or calendarName.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scheduleIdYesa string that will be trimmed
ownerNoa string that will be trimmed
titleNoa string that will be trimmed
descriptionNoNew schedule description. Pass null to clear; empty string is also accepted.
meetingDurationNoNew default meeting duration in minutes.
meetingIntervalNoNew minimum interval between meetings in minutes.
availabilityNo
timeZoneNoa string that will be trimmed
calendarIdNoa string that will be trimmed
calendarNameNoa string that will be trimmed

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior3/5

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

Annotations indicate idempotentHint=true and destructiveHint=false, so the description need not repeat safety info. However, the description adds no behavioral context beyond the fact that it updates fields. It doesn't mention side effects, authorization requirements, or irreversible actions, which would be valuable given the mutation.

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?

The description is a single, front-loaded sentence that efficiently conveys the tool's purpose and scope. No unnecessary words.

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?

Given the presence of a detailed input schema, output schema, and annotations, the description is largely complete. It highlights the key fields but could mention that scheduleId is required and clarify the calendarId/calendarName mutual exclusivity constraint. Still, it provides sufficient context for an AI agent.

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 90%, so parameters are well-documented in the schema. The description lists the updatable fields but adds minimal new meaning beyond what's already in the property descriptions. Baseline 3 is appropriate.

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?

The description clearly states the tool updates a calendar schedule and lists supported fields. It uses a specific verb ('Update') and a specific resource ('calendar schedule'), which distinguishes it from related tools like 'create_schedule' and 'delete_schedule'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when to prefer this tool over other schedule-related tools, or any limitations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dearlordylord/huly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server