Skip to main content
Glama

Update a loop

update_loop
DestructiveIdempotent

Change a loop's fields. Only the fields you pass change; their previous values are overwritten.

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": {
      "loop_id": "<loop_id>"
    },
    "name": "update_loop"
  }
}

Input Schema

NameRequiredDescriptionDefault
dowNoDays of the week as a bitmask: Monday=1, Tuesday=2, Wednesday=4, Thursday=8, Friday=16, Saturday=32, Sunday=64. 127 = every day, 31 = weekdays. 0 = none (use with cron or every_days).
cronNoCron schedule, 5 fields; only the date fields (day of month, month, weekday) matter: minute and hour are ignored, so write them as "0 0" (e.g. "0 0 * * 1" = Mondays). Alternative to dow and every_days (one schedule system at a time). Do not use "*/N" in the day field for "every N days": it restarts each month; use every_days.
nameNoLoop name.
loop_idYesThe loop's id (from list_loops).
end_dateNoLast day it applies, YYYY-MM-DD. null clears it.
is_activeNofalse pauses it without deleting it.
loop_typeNo"loop" (default): advances to the next task at each arming pass. "schedule": only on its dow, cron or every_days days (exactly one of them).
every_daysNoStrict interval: due every N days, counted from start_date (the anchor; defaults to today in the user's time zone). A missed day does not shift the cycle. Schedule tasks/loops only, and instead of dow and cron (send dow 0 / cron null with it). null removes it.
start_dateNoFirst day it applies, YYYY-MM-DD; with every_days, the first day of the interval. null clears it.
descriptionNoLonger notes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful patch semantics — only passed fields change, others remain, passed values are overwritten (irreversible) — but it omits what breaking a schedule means, validation failure behavior, and permission needs.

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?

Two short sentences, front-loaded with the core action and immediately followed by the key mutation semantic. No filler, no repetition of schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 10 parameters and rich schema docs plus annotations covering safety, the description is adequate but thin for a destructive mutation: it does not mention mutual exclusivity of dow/cron/every_days, null-clearing behavior, or failure modes. The heavy lifting is done by the schema, leaving the description just sufficient.

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 semantics for dow bitmasks, cron quirks, every_days anchoring, and null-clears behavior, so the schema carries the parameter burden. The description adds nothing about parameters beyond restating patch semantics, so baseline 3 applies.

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?

Clearly states a verb ("Change") and resource ("a loop's fields"), so the agent knows this is a mutation of an existing loop. It does not distinguish itself from siblings like create_loop or update_task, but the purpose itself is unambiguous.

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?

There is no guidance on when to use this versus alternatives such as update_task, create_loop, or delete_loop, and no prerequisites (e.g., needing a valid loop_id from list_loops) are stated. The patch-semantics sentence is behavioral, not usage guidance.

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