Skip to main content
Glama

alert

Inspect or respond to visible system prompts on iOS or Apple TV: retrieve the message and button labels, then accept or dismiss via a specific button.

Instructions

Inspect or respond to a visible system alert on iOS or Apple TV (get, accept, or dismiss). get returns the message and the button labels.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes'get' returns the alert message and button labels; 'accept' taps a button (first by default); 'dismiss' taps a button (by default a Cancel, Don't Allow or Not Now style button, else the last).
buttonNoSpecific button label to tap (case-insensitive). Omit to use the default for the action.
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint=false is consistent with a tool that can tap buttons; no contradiction. The description adds value beyond annotations by stating what `get` returns (message plus button labels) despite there being no output schema, though it says nothing about what accept/dismiss return or what happens when no alert is visible.

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?

Two compact sentences, front-loaded with the purpose and the action set, with the return note appended where it belongs. No filler or redundant restatement of the tool name.

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 three-parameter, no-output-schema tool, the description covers purpose, action semantics, and the one return value. Minor gap: outcomes of accept/dismiss and failure behavior when the alert is absent are unstated, but they are not essential to invoke it correctly.

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%, and every parameter detail in the description (get's return content, default button selection, session fallback) is already spelled out in the schema's own descriptions. Baseline 3 applies when the schema carries the parameter burden.

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 names a specific resource (visible system alert), the platforms (iOS, Apple TV), and enumerates the three modes (get, accept, dismiss). This distinguishes it from generic input siblings such as tap or press without the agent needing to open 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 Guidelines4/5

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

The word 'visible' establishes the precondition that an alert must already be on screen, and the parenthetical routes the agent among the three actions. It stops short of naming an alternative for the negative case (e.g., use find or screenshot when no alert is present).

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