Skip to main content
Glama

Create a loop

create_loop

Create an empty loop (a queue of tasks). Add tasks with enqueue_task.

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": {
      "name": "<name>"
    },
    "name": "create_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.
nameYesLoop name.
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

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and closed-world, so the safety profile is covered. The description adds one useful behavioral fact: the created loop is empty and does nothing until tasks are enqueued. It says nothing about whether a new loop is active by default, whether names must be unique, or what happens on duplicate creation (relevant since idempotentHint is false).

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 compact sentences, front-loaded with the verb and resource, with the follow-up action in the second sentence. No filler and no restatement of the title.

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?

The schema is fully documented, so scheduling complexity is handled, but for a create tool the description omits the return value (no output schema exists) — an agent needs to know whether the new loop's identifier comes back in order to call enqueue_task. That missing hand-off detail is the main completeness gap.

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% and the parameter docs are unusually thorough, including dow bitmask examples and the cron/every_days exclusion rule, so the schema carries the semantics. The description adds no parameter meaning beyond it; baseline 3 applies.

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 ('Create an empty loop'), immediately glosses the resource as 'a queue of tasks', and names the sibling that fills it ('Add tasks with enqueue_task'). An agent can distinguish this from create_task and enqueue_task without opening any schema.

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

Usage Guidelines3/5

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

The pointer to enqueue_task makes the create-then-populate workflow clear, which is genuine usage guidance. However, it never says when to use create_loop versus create_task, nor when to pick 'loop' versus 'schedule' loop_type at the top level, so the choice among alternatives is only implied.

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