Skip to main content
Glama

Update product schedule

suppco_update_product_schedule
DestructiveIdempotent

Use this when the user wants to change when or how they take a product that is already in their stack. Replaces that product's schedule: time-of-day amounts, daily, specific-days or every-other-day timing, as-needed, with food, and timing notes.

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": {
      "product_id": "<product_id>",
      "schedule": "<schedule>"
    },
    "name": "suppco_update_product_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
scheduleYesJSON array of time-slot assignments, e.g. [{"activity":"morning","units":2},{"activity":"bedtime","units":1}]. "units" is in the product's serving unit as user_schedule shows it (capsules, tablets, scoops, mL, ...) — NOT servings. For a tincture whose serving_size is 0.7 mL, one serving is 0.7, not 1. Valid activities: morning, midday, evening, bedtime, workout, unscheduled.
as_neededNoWhether the product is taken as needed (true/false). Omit to keep the current value.
with_foodNoWhether the product should be taken with food (true/false). Omit to keep the current value.
product_idYesProduct slug or UUID
schedule_daysNoArray of day names (e.g. ["monday","wednesday","friday"]) for specific_days schedule_type
schedule_typeNoSchedule type: daily, specific_days, or every_other_day
schedule_notesNoBrief timing instructions that the schedule cannot capture (e.g., "take 2 hours apart from calcium", "take on empty stomach 30 min before bed"). Set to empty string to clear.
new_daily_amountNoONLY when the user explicitly asked to take a different amount per day: the new daily total they asked for, in the same units as the schedule. Must equal the schedule total. Omit for timing changes — a schedule whose total differs from the current daily amount is rejected without it.
every_other_day_startNoWhen to start every_other_day schedule: "today" or "tomorrow"
attribute_change_requestedNoSet true ONLY when the user asked to change with_food or as_needed. Without it, a with_food/as_needed value that differs from the current one is rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / as_needed / description
      Previous value: -"Whether the product is taken as needed (true/false). Omit to keep the current value — only pass it when the user asked to change it."New value: +"Whether the product is taken as needed (true/false). Omit to keep the current value."
    • addedInput schema / properties / attribute_change_requested
      Added value: +{
      +  "description": "Set true ONLY when the user asked to change with_food or as_needed. Without it, a with_food/as_needed value that differs from the current one is rejected.",
      +  "type": "string"
      +}
    • removedInput schema / properties / change_daily_amount
      Removed value: -{
      -  "description": "Set true ONLY when the user asked to change how many units they take per day. Without it, a schedule whose total differs from the current daily amount is rejected, so timing changes keep the same total.",
      -  "type": "string"
      -}
    • addedInput schema / properties / new_daily_amount
      Added value: +{
      +  "description": "ONLY when the user explicitly asked to take a different amount per day: the new daily total they asked for, in the same units as the schedule. Must equal the schedule total. Omit for timing changes — a schedule whose total differs from the current daily amount is rejected without it.",
      +  "type": "string"
      +}
    • changedInput schema / properties / schedule / description
      Previous value: -"JSON array of time-slot assignments, e.g. [{\"activity\":\"morning\",\"units\":2},{\"activity\":\"bedtime\",\"units\":1}]. \"units\" is the number of capsules/tablets/scoops for that time slot — NOT servings. Valid activities: morning, midday, evening, bedtime, workout, unscheduled."New value: +"JSON array of time-slot assignments, e.g. [{\"activity\":\"morning\",\"units\":2},{\"activity\":\"bedtime\",\"units\":1}]. \"units\" is in the product's serving unit as user_schedule shows it (capsules, tablets, scoops, mL, ...) — NOT servings. For a tincture whose serving_size is 0.7 mL, one serving is 0.7, not 1. Valid activities: morning, midday, evening, bedtime, workout, unscheduled."
    • changedInput schema / properties / with_food / description
      Previous value: -"Whether the product should be taken with food (true/false). Omit to keep the current value — only pass it when the user asked to change it."New value: +"Whether the product should be taken with food (true/false). Omit to keep the current value."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description reinforces this by saying it 'Replaces that product's schedule' and enumerating the replaced facets (time-of-day amounts, cadence, as-needed, with food, notes), so the agent knows this is full-replacement rather than merge. It does not surface the schema's rejection rules or what is returned, but the core mutation semantics are disclosed.

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?

Two sentences, front-loaded with the usage trigger before the resource description, with no filler. The second sentence's enumeration partially restates schema fields, which keeps it just short of maximally efficient.

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 10-parameter destructive mutation with no output schema, the description covers the selection context and the replacement scope, while the fully-described schema covers parameter mechanics and rejection behavior. Missing only a note on what the call returns (e.g., the resulting schedule) or confirmation of whether changes are reversible.

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 100%, including detailed guidance for schedule units and the new_daily_amount/attribute_change_requested guards, so the schema does the heavy lifting. The description only echoes those fields as a category list and adds no unit, format, or validation nuance of its own. Baseline 3 is appropriate.

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?

States a specific verb ('change when or how they take a product') and scopes it to a product 'already in their stack,' which separates it from stack-addition siblings like suppco_add_to_stack. The second sentence enumerates exactly which schedule facets are replaced, so the resource is unambiguous. It stops short of naming a sibling alternative outright.

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 this when the user wants to change when or how they take a product that is already in their stack' is a genuine when-to-use trigger with an implicit exclusion (products not yet in the stack). No explicit when-not clause or named alternative such as remove_from_stack or get_my_schedule for read-only inspection.

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.

Resources