Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_sms_code_get

Read-only

Retrieves the current SMS verification code for a purchased phone number, optionally polling up to 120 seconds and ignoring older messages to complete verification.

Instructions

Read the latest SMS and code of one purchased number. waitSeconds (max 120) polls until a code arrives or the number stops waiting. receivedAfter (ISO time with timezone of the current send) ignores earlier SMS and SMS without a valid time; onlyNew ignores codes already present at the first pull. To type the code into a page, use nex_sms_code_fill.

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>"
    },
    "name": "nex_sms_code_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
telYes
onlyNewNo
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.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds the important behavioral facts beyond that: the call can block while polling for up to 120 seconds, polling ends when a code arrives or the number stops waiting, and receivedAfter silently drops SMS lacking a valid timestamp. These are exactly the latency and filtering semantics an agent needs before calling.

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?

Four compact sentences, front-loaded with what the tool returns, then per-parameter semantics, then sibling routing. No filler, and each clause carries operational meaning.

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?

No output schema exists, and the description partly compensates by saying it returns the latest SMS and code. What is returned when polling times out or the number stops waiting is left unstated, which is the main remaining ambiguity for an otherwise complete definition.

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?

With schema description coverage at 0%, the description carries the parameter burden and mostly succeeds: it explains waitSeconds as a polling duration capped at 120, receivedAfter as an ISO time with the timezone of the current send plus its filtering side effects, and onlyNew as ignoring codes present at the first pull. Only tel is left to inference as the purchased number, which is a minor gap.

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 specific verb (read) and resource (the latest SMS and code of one purchased number), with the scope of exactly one number made explicit. It is clearly distinguishable from siblings like nex_sms_record_list and nex_sms_code_fill, and the last sentence explicitly routes the typing use case elsewhere.

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 closing sentence names an alternative (nex_sms_code_fill) and the condition that selects it, and the parameter notes imply when to use waitSeconds vs a single pull. It stops short of stating exclusions such as when to prefer nex_sms_record_list for historical records, so it is strong but not exhaustive.

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