Skip to main content
Glama

Get Task Lock

get_task_lock
Read-onlyIdempotent

Read the user's Task Lock settings (iPhone/iPad only): whether it is on, from what time it locks, onlyDueByNow, whether 15-minute breaks are allowed, the saved app lists (name and how many apps/categories/websites each blocks) with the active one, and the device's last reported status (locked or not, tasks left, when it was reported). The apps in a list are chosen on the phone and are not visible here. Use before set_task_lock or switch_task_lock_list.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered and the description is free to add domain behavior. It does: the platform restriction, the shape of the returned payload, and the important caveat that the apps inside a list "are chosen on the phone and are not visible here" — a real limitation an agent would otherwise misreport. It stops short of stating freshness of the last-reported status or what happens if the device has never reported.

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?

Purpose is front-loaded, and the long enumeration sentence is dense but every clause corresponds to a distinct returned field. The trailing usage sentence is a separate, clearly scoped statement. A bulleted field list would scan faster, but nothing is padding.

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

Completeness5/5

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

There is no output schema, so the description must carry the return-value burden — and it does, listing every setting and the device status with its components. Combined with the platform caveat and the apps-not-visible limitation, an agent has everything needed to call it and interpret the result.

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 zero parameters, so the baseline is 4; the empty schema leaves nothing for the description to clarify. The description does not waste words restating arguments, which is correct here.

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?

"Read the user's Task Lock settings" gives a specific verb and resource, then enumerates the exact fields returned (on/off, lock time, onlyDueByNow, 15-minute breaks, saved app lists with the active one, last reported device status). The closing sentence names the two sibling tools it feeds into, so an agent can separate it from set_task_lock and switch_task_lock_list 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 Guidelines4/5

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

"Use before set_task_lock or switch_task_lock_list" supplies explicit sequencing guidance and names the alternatives. The "iPhone/iPad only" note acts as a platform precondition. What is missing is a when-not case (e.g. what to do on other platforms, or whether calling it is redundant when the user already knows their settings).

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