Skip to main content
Glama

Run the arming pass

arm_all
Destructive

Run the arming pass the user asked for, in the user's time zone. 1) A scheduled "drop" task still armed from an earlier day is skipped automatically (missed); one armed today is kept; "reschedule" tasks stay armed. 2) Arms every active scheduled task due today that is not armed, except one the user already checked or skipped today. 3) Moves each active loop to its next task, except a loop whose current task is still armed and a schedule loop on a day outside its schedule. A second run on the same day skips nothing and does not bring back scheduled tasks checked or skipped today, but it still advances every loop whose current task is no longer armed (checked, skipped, unarmed or deleted since): not idempotent. Only when the user asks: arming is the user's act.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "arm_all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Far exceeds the annotations: it spells out exactly which tasks are skipped (previous-day drops), which are kept (armed today, reschedule tasks), what happens on a second same-day run, and states 'not idempotent' plus the loop-advancement rule. This aligns with destructiveHint=true and idempotentHint=false and adds real operational context about side effects and repeat-run behavior.

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?

Front-loads the action and the user-intent gate, then uses numbered rules for the multi-part behavior, with the non-idempotence caveat at the end. Dense but every sentence carries rules an agent needs; slightly long and could be tightened.

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 zero-parameter mutation with no output schema, the description covers side effects, skip logic, and repeat-run semantics thoroughly. It does not say what the call returns (e.g., whether armed/skipped counts are reported), which is a minor remaining gap.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline applies. The description appropriately spends its space on behavior instead of inventing parameter detail.

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 action (run the arming pass) and then defines it concretely through the numbered rules: arming due scheduled tasks and advancing loops. It does not name a sibling or explicitly contrast itself with check_task/skip flows, so it stops short of full differentiation, but the purpose is unmistakable.

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?

Gives a clear gating condition: 'Only when the user asks: arming is the user's act.' That is strong when-to-use guidance. It does not state when-not conditions relative to alternatives (e.g., don't use this to check or skip tasks yourself), so it is not fully explicit.

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