Skip to main content
Glama
Dominic-DK

Askew

by Dominic-DK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

askew_run

Execute a pre-defined Apple Shortcut route on your iPhone, iPad, or Mac and retrieve its decrypted result, even while the device is locked.

Instructions

Run a Shortcut (a 'route') on the user's iPhone, iPad or Mac and return its result. Works while the phone is locked: the relay pushes a notification, one dispatcher automation runs the target Shortcut, and the result comes back end-to-end encrypted. Behavior: call askew_list_routes first; each route lists an inputExample and the input MUST use exactly those keys (dates 'YYYY-MM-DD HH:mm'), otherwise the call is rejected before anything runs. Waits up to wait seconds (default 45) and returns status (done | failed | unknown | pending), the decrypted result text and a timeline. If status is 'unknown' or 'pending', poll with askew_get_run using the returned jobId. Usage: one route per call; do not retry a failed job blindly — read the error text, fix the input, or ask the user. Use idempotencyKey when you must retry a network error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoSeconds to wait for the result, 0–60 (default 45). 0 returns immediately with status 'pending'; poll with askew_get_run. A locked phone usually answers within 1–3 seconds.
inputYesInput for the Shortcut. MUST follow the route's inputExample from askew_list_routes: the same JSON keys, dates as 'YYYY-MM-DD HH:mm', send "" for keys you do not need. A JSON object for routes whose example is an object; a plain string only for routes whose example is a string. A mismatched input is rejected before anything runs on the phone.
routeIdNoRoute id from askew_list_routes (e.g. 'rt_…'). Give either routeId or routeName; routeId wins when both are present.
routeNameNoRoute name from askew_list_routes (e.g. 'calendar.add'). Case-sensitive. Use this when you know the name but not the id.
idempotencyKeyNoOptional client-chosen key (≤200 chars). Re-sending the same key returns the existing job instead of running the Shortcut again; use it for retries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"같은 요청을 다시 보낼 때 같은 키를 쓰면 중복 실행되지 않음"New value: +"Optional client-chosen key (≤200 chars). Re-sending the same key returns the existing job instead of running the Shortcut again; use it for retries."
    • changedInput schema / properties / input / description
      Previous value: -"Input for the Shortcut. MUST follow the route's inputExample from askew_list_routes (same JSON keys; dates as 'YYYY-MM-DD HH:mm'). A JSON object for routes whose example is an object; a plain string only for routes whose example is a string."New value: +"Input for the Shortcut. MUST follow the route's inputExample from askew_list_routes: the same JSON keys, dates as 'YYYY-MM-DD HH:mm', send \"\" for keys you do not need. A JSON object for routes whose example is an object; a plain string only for routes whose example is a string. A mismatched input is rejected before anything runs on the phone."
    • addedInput schema / properties / routeId / description
      Added value: +"Route id from askew_list_routes (e.g. 'rt_…'). Give either routeId or routeName; routeId wins when both are present."
    • addedInput schema / properties / routeName / description
      Added value: +"Route name from askew_list_routes (e.g. 'calendar.add'). Case-sensitive. Use this when you know the name but not the id."
    • changedInput schema / properties / wait / description
      Previous value: -"결과를 기다릴 초(0이면 즉시 반환)"New value: +"Seconds to wait for the result, 0–60 (default 45). 0 returns immediately with status 'pending'; poll with askew_get_run. A locked phone usually answers within 1–3 seconds."
  2. First observedv0.1.2

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and meets it impressively. It discloses locked-phone execution, end-to-end encryption, rejection of mismatched input before any run, wait/polling behavior, status values, and the meaning of idempotencyKey for retries.

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?

The description is dense but every sentence adds necessary operational detail, and it is well structured with purpose first, then behavior, then usage guidance. There is no filler or redundant repetition of schema fields.

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?

For a complex async execution tool with no annotations and no output schema, the description is remarkably complete: it explains how results arrive, what statuses to expect, how to poll, how to handle failures, and how to retry safely. Nothing critical is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds meaning beyond the schema: input must use exactly the route's example keys with 'YYYY-MM-DD HH:mm' dates, empty strings for unused keys, routeId precedence over routeName, and the recommended use of idempotencyKey for network-error retries.

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?

The description opens with a specific verb and resource: "Run a Shortcut (a 'route') on the user's iPhone, iPad or Mac and return its result." It clearly separates this from sibling tools by naming askew_list_routes as a prerequisite and askew_get_run for polling, so an agent can tell what this tool is for.

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?

The description gives explicit when-to-use guidance: call askew_list_routes first, match input to the route's inputExample, and poll with askew_get_run when status is 'unknown' or 'pending'. It also gives when-not-to-retry guidance: don't blindly retry a failed job, read the error and fix the input.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools