Skip to main content
Glama
Dominic-DK

Askew

by Dominic-DK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

askew_variables_set

Safely store a string or JSON object for your iPhone Shortcuts to retrieve later. The value is encrypted on your device, so only ciphertext reaches the relay, and writing an existing name replaces it.

Instructions

Write a variable shared between the agent and the user's phone. The value (a string or a JSON object) is encrypted with the account key before leaving this computer, and the phone's Shortcuts read it with the same key; the relay stores only ciphertext. Writing an existing name replaces the value; there is no versioning. Returns the name and update time. Errors: the account key has not arrived yet (ask the user to open Settings → Connector → Resend key). Use it for data a Shortcut should pick up later (e.g. 'today.plan'), not for large blobs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesVariable name (case-sensitive), e.g. 'home' or 'today.plan'. Writing an existing name replaces its value; the name is authenticated with the value, so it cannot be read back under another name.
valueYesThe value to store: a plain string, or a JSON object (stored as JSON text). Encrypted with the account key before it leaves this computer; the phone's Shortcuts read it with the same key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"Variable name (case-sensitive), e.g. 'home' or 'today.plan'. Writing an existing name replaces its value; the name is authenticated with the value, so it cannot be read back under another name."
    • addedInput schema / properties / value / description
      Added value: +"The value to store: a plain string, or a JSON object (stored as JSON text). Encrypted with the account key before it leaves this computer; the phone's Shortcuts read it with the same key."
  2. First observedv0.1.2

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carres the full burden — and it delivers: encryption before leavg the computer, relay stores only ciphertext, overwrite-on-existing-name with no versioning, return values, and an actionable error case with user remediation steps. Exemplary beavioral disclosure.

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?

Every sentence carries distinct information: purpose, security model, overwrite beavior, return value, error handling, and usage limits. The purpose is front-loaded and nothing is redundant or filler.

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 mutation tool with no annotations and no output schema, the description covers all decision-relevant aspects: what it writes, how it protects data, what happens on conflict, what it returns, how to handle the key-not-arrived error, and suitable payload sizes. Nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3; the schema already documents name (case-sensitive, overwrite beavior) and value (string or JSON object, encrypted). The description reinforces these facts but adds little parameter-specific meaning beyond the schema.

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?

Opens with a specific verb-resource statement — 'Write a variable shared between the agent and the user's phone' — so an agent knows exactly the operation and resource. The write operation is clearly distinct from sibling askew_variables_get and the run/inbox tools.

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 explicit context — 'Use it for data a Shortcut should pick up later (e.g. 'today.plan')' — and an exclusion ('not for large blobs'). It does't explicitly name askew_variables_get as the read counterprat, so the when-not-to-use guidance is slightly less direct than it could be.

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