Skip to main content
Glama

ios_siri_tasks

Retrieve recent Siri voice commands and execution traces received by the gateway to inspect delivered requests and troubleshoot voice-triggered actions.

Instructions

Read recent Siri voice commands & execution traces received by the gateway.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies a read operation through the verb 'Read'. It says nothing about ordering, retention window, pagination, permissions, or what 'execution traces' actually contain, leaving the agent to guess at behavior for anything beyond a simple fetch.

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?

One short sentence with no filler and the resource stated up front. It is efficiently written, though the brevity comes at the cost of the missing detail noted in other dimensions rather than being a structural flaw.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the tool is a simple single-optional-parameter read. However, with no annotations and an undocumented limit parameter, the definition leaves the agent without enough context to know how results are scoped or ordered.

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

Parameters2/5

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

The single parameter 'limit' has 0% schema description coverage, and the description never mentions it. 'Recent' loosely hints that the result set is bounded, but neither the meaning of the bound (count vs. time window), its default of 10, nor its maximum is clarified anywhere the description covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Read') and a specific resource ('recent Siri voice commands & execution traces received by the gateway'), which is enough for an agent to distinguish this from UI-interaction siblings like ios_tap or ios_ui_dump. It stops short of naming a neighboring diagnostic tool such as ios_lowlevel_telemetry, so the boundary with other read-style tools is left implicit.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated preconditions, and no exclusions or alternatives. The word 'recent' implies a retrospective diagnostic lookup, but the agent must infer on its own when this tool is preferable to ios_lowlevel_telemetry or ios_ui_dump.

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