frida-ios-mcp

by YPYT1

Overview Schema Source Related Servers Discussions Admin

JavaScript

human_pause

Add random pauses between actions to simulate human-like timing, with adjustable min and max sleep durations.

Instructions

Random step gap sleep (fleetcontrol human_pause). Not typing delay — use between actions.

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

Input Schema

Name	Required	Description	Default
`maxMs`	No	Default 500
`minMs`	No	Default 200

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Without annotations, the description reveals basic behavior (random sleep, min/max parameters) but omits details like blocking nature, interruptibility, or side effects. It adds some value by stating it's not typing delay.

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 very concise with two sentences, front-loading the purpose and key usage hint. No unnecessary words.

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?

For a simple tool with two number parameters and no output schema, the description provides adequate context on usage. However, it could mention that it blocks or returns nothing, and lacks a distinction from the similar sibling 'wait'.

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 input schema covers both parameters with basic default descriptions, but the tool description adds no further meaning. The randomness is implicit from the tool purpose but not explicitly linked to parameters.

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 clearly identifies the tool as a random sleep between actions, explicitly distinguishes it from typing delay, and uses specific verbs and resource terms ('random step gap sleep').

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

Usage Guidelines3/5

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

The description advises using it between actions and clarifies it is not a typing delay, but does not discuss when not to use it or compare with sibling tools like 'wait'.

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