Skip to main content
Glama

Switch Task Lock app list

switch_task_lock_list
Idempotent

Make another saved app list the one Task Lock blocks on the user's iPhone/iPad, by its name (case-insensitive) or id from get_task_lock. Only lists the user already saved in Weeklane on the phone can be chosen; new lists and the apps in them are set up on the phone. This does not turn Task Lock on or off (use set_task_lock). Can be reverted with undo_last_change.

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": "switch_task_lock_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName of a saved app list, e.g. "Social" (case-insensitive).
listIdNoId of a saved app list from get_task_lock (instead of the name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is largely covered. The description adds genuinely useful context beyond that: case-insensitive matching, the phone-side prerequisite, and reversibility through undo_last_change. It does not cover failure behavior (unknown name/id, or what happens if both name and listId are supplied), which leaves a real gap for a mutation tool.

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-loaded with the action and its identifier, then constraints and the sibling pointer. Three sentences, each carrying information, with only minor duplication of schema-stated details such as case-insensitivity.

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 two-parameter mutation with no output schema, the description covers the operation, prerequisites, scope limits, sibling routing, and rollback. The remaining gaps are edge-case resolution (identifier not found, both identifiers given), which are minor for this complexity level.

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 coverage is 100%, so both parameters are already documented in the schema, including the case-insensitive name and the get_task_lock id source. The description restates those facts and hints that name and id are alternatives, but neither source explicitly states precedence or mutual exclusivity, so the meaning added is marginal. 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?

Specific verb and resource: makes a saved app list the active one Task Lock blocks, identified by name or id. It immediately distinguishes itself from set_task_lock (enable/disable) and from list-management work done on the phone, so an agent can pick it apart from siblings without opening the schema.

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

Usage Guidelines5/5

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

States explicit preconditions (the list must already be saved in Weeklane on the phone; new lists and their apps are created on the device), an explicit exclusion with a named alternative ('This does not turn Task Lock on or off (use set_task_lock)'), and a recovery path via undo_last_change. This is the full when/when-not/alternative triad.

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