Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_sms_code_fill

Waits for an SMS code sent to a phone number and types it into the page, keeping the code out of the conversation. Use receivedAfter and waitSeconds to target the expected code and wait limit.

Instructions

Wait for one number's SMS code and type it into the page, so the code never passes through the conversation. Flow: enter the number on the site, note the send time, click send, take a snapshot for the code input ref, then call this with receivedAfter set to that send time (ISO with timezone). Waits up to waitSeconds (default and max 120). onlyNew ignores codes already present at the first pull; use it only after a resend. submit=true presses Enter. A confirmed code timeout allows a replacement number; a purchase timeout is not a code timeout.

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": {
      "tel": "<tel>",
      "target": "<target>"
    },
    "name": "nex_sms_code_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
telYes
pageIdNoDefaults to the active page
submitNo
targetYesSnapshot ref (e12) or unique CSS selector
onlyNewNo
sessionIdNoDefaults to the active session
waitSecondsNo
receivedAfterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.11.3
    • changedInput schema / properties / receivedAfter / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
  2. Addedv2026.10.24

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the blocking wait behavior and its cap (default and max 120 seconds), the page-mutating side effects (types the code into a target, optional Enter), and failure semantics distinguishing a confirmed code timeout from a purchase timeout. It omits what a successful call returns and how a timeout is surfaced to the caller.

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?

Purpose is front-loaded, then a clearly labeled 'Flow:' sequence, then the parameter caveats. Dense but nearly every clause carries operational meaning; the closing timeout sentence is the only genuinely awkward, run-on part.

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 an 8-parameter mutation tool with no annotations and no output schema, this covers the calling workflow, timing, and failure modes well. The remaining gap is the return value and error surface — an agent still doesn't know what comes back on success, or whether the await fails or returns a status on timeout.

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 only 38%, but the description compensates for the most consequential parameters: receivedAfter must be the noted send time in ISO with timezone, waitSeconds carries the default and max, onlyNew has precise semantics (ignore codes present at the first pull, only after a resend), and submit maps to pressing Enter. tel format and target's selector-vs-ref distinction are restated from the schema rather than extended.

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?

States a concrete verb and resource — wait for one number's SMS code and type it into the page — and immediately frames the differentiator versus a code-retrieval sibling, that the code never passes through the conversation. An agent can tell what this does and why it exists without opening 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?

Gives an explicit prerequisite flow (enter number, note send time, click send, snapshot for the code input ref, then call) and conditional guidance for onlyNew ('use it only after a resend') and submit. It never names an alternative sibling such as nex_sms_code_get or states when not to use this tool, so it falls short of full when/when-not routing.

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