frida-ios-mcp

by YPYT1

Overview Schema Source Related Servers Discussions Admin

JavaScript

set_otp

Fill TikTok OTP input fields by passing the complete code string, such as 123456, to automate verification code entry.

Instructions

Fill TikTok OTP (TMVerificationCodeInputView / TUXPinField). Pass full code string e.g. 123456.

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": {
      "code": "<code>"
    },
    "name": "set_otp"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	OTP digits
`source`	No	Debug tag, default mcp

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'Fill' without disclosing side effects, prerequisites (e.g., being on the OTP screen), or whether it clears existing text. Minimal behavioral context.

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 a single, front-loaded sentence with no wasted words. It immediately states the core action and target, making it easy to parse.

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 UI-filling tool with two parameters and no output schema, the description is adequate but lacks context about preconditions (e.g., requiring the OTP screen to be visible) and any return behavior.

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

Parameters4/5

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

Schema coverage is 100% and description adds value with an example ('Pass full code string e.g. 123456') and specifies the target UI elements, going beyond the schema's 'OTP digits' description.

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 states the action ('Fill TikTok OTP'), specifies the target UI elements ('TMVerificationCodeInputView / TUXPinField'), and gives an example input. It differentiates from sibling tools that handle generic text input or other actions.

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 implies usage for TikTok OTP fields but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives from the sibling list like 'type_text' for general text entry.

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