Skip to main content
Glama

update_schedule

Update an existing audit schedule: change target URL, audit depth, cron expression, or pause via enabled=false. Set score-drop alerts and notification settings.

Instructions

[schedule] Partial update of an audit schedule (all fields except id are optional). Use list_schedules to look up ID. Common: pause via enabled=false, change cadence via cron_expression, add score-drop alerts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSchedule ID to update (from list_schedules)
urlNoReplace the target URL being audited
modeNoAudit depth: basic (fastest, core checks), standard (balanced), deep (most thorough, slower)
cron_expressionNo5-field cron expression for run cadence (e.g. "0 2 * * *" = daily at 02:00 UTC)
nameNoHuman-readable label shown in dashboards
enabledNoMaster switch: set false to pause the schedule without deleting it
alert_on_failNoSend an alert when a scheduled audit run fails to complete
alert_on_score_dropNoSend an alert when the overall score drops below score_threshold from the previous run
score_thresholdNoScore (0-100) below which alert_on_score_drop fires — e.g. 80 alerts when the audit scores under 80
webhook_urlNoOverride the webhook URL used for alerts (defaults to the account's default webhook)
email_recipientsNoComma-separated email addresses to notify on alerts

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate this is a mutation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds that it is a partial update (affects only provided fields) and provides examples like pausing via enabled=false, which is beyond the annotations.

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 extremely concise: two sentences. The first sentence states the purpose, the second provides prerequisite and common examples. 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 11 parameters, mutation nature, and existence of an output schema, the description covers prerequisites, common use cases, and partial update semantics. It does not detail return values (handled by output schema) or side effects, but is sufficient for typical usage.

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 baseline is 3. The description adds value by linking parameters to common tasks (e.g., 'pause via enabled=false, change cadence via cron_expression, add score-drop alerts'), providing meaningful context beyond individual parameter descriptions.

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 'Partial update of an audit schedule', specifying the verb (update) and resource (audit schedule). It distinguishes from sibling tools like create_schedule, delete_schedule, get_schedule, and list_schedules by being the sole update operation.

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?

The description provides context for when to use this tool, advising to 'Use list_schedules to look up ID' and giving common use cases (pause, change cadence, add alerts). It does not explicitly state when not to use, but the examples cover typical modifications.

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/VertaaUX/mcp-server'

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