IMEILookup

Export the complete server-generated CSV for a batch belonging to the connected user. Supply an actual batchId from the conversation or list_batches. The current response contains CSV text; do not promise a server-hosted download URL or asynchronous export job. With compatible ChatGPT file tools, save the complete returned content unchanged as a downloadable CSV. Preserve all rows and returned columns, and report failures or truncation clearly. Do not fetch every full order just to rebuild this native batch export. Args: batchId: The batch ID whose orders to export.

Retrieve the full result of an order belonging to the connected user by its returned order ID. Present actual fields in copyable text unless another format or summary is requested. Do not infer missing model, warranty, or status values; omit internal roles from ordinary replies. Keep batch/order references available and show them when useful. Args: id: The order ID.

Retrieve the connected user's current available account credits. Report the returned balance without inventing a currency or changing account credit. Args: ctx: MCP request context (used to forward the OAuth token).

Retrieve the connected user's account profile and returned credit balance. Present requested profile fields accurately; omit internal roles, authentication secrets, and unnecessary internal IDs from ordinary replies. Does not place orders. Args: ctx: MCP request context (used to forward the OAuth token).

Retrieve the connected user's batches with supported pagination and filters. Preserve batch titles. Distinguish Pending and Completed batches from each order's status. Verify ordering before identifying the latest batch and use all needed pages for complete totals. Date arguments accept YYYY-MM-DD; apply exact-time filtering to returned creation timestamps when requested. Keep batch IDs available for tool calls and show them when useful for tracking, exporting or support. Args: page: Page number (0-based). size: Number of batches per page (min 5, max 5000). status: One of Pending, Completed. serviceId: Filter by service ID. title: Filter by batch title. batchId: Filter by batch ID. from_date: Start date in YYYY-MM-DD format (no time or timezone). Must be on or before to_date. to_date: End date in YYYY-MM-DD format (no time or timezone). sortBy: Only "Created" is supported.

Retrieve the connected user's orders using the exposed pagination, service/status/batch/date/search filters. The search array supports IMEIs and serial numbers; serial matching is case-insensitive. Date filters currently accept YYYY-MM-DD. For hours/minutes, fetch the necessary dates/pages and filter returned creation timestamps against one captured time window. Do not rely on IMEI/status server sorting. Retrieve every relevant page and sort the complete set in ChatGPT when requested; label partial results if complete retrieval is unavailable. For large identifier lists, split read-only searches and merge pages by order ID, preserving repeated historical checks. Show requested result details without internal roles. Keep batch IDs available and show them when useful. Args: page: Page number (0-based). size: Number of orders per page (max 5000). orderStatus: One of Failed, Waiting, Success, Processing. serviceId: Filter by service ID. batchId: Filter by batch ID. batchName: Filter by batch name. from_date: Start date in YYYY-MM-DD format (no time or timezone). Must be on or before to_date. to_date: End date in YYYY-MM-DD format (no time or timezone). sortBy: One of imei, order, status, updated. search: IMEIs or serial numbers to search for; serial matching is case-insensitive.

List available device-check services, IDs, prices, and returned descriptions or sample results. Supports page (0-based) and size only. Follow pagination when needed for a complete comparison. Use the user's requested outcome and selection criteria to identify a compatible service; an exact service name is not required when the user delegates selection. Clarify genuinely ambiguous requests before paid ordering. Sample output is illustrative, not a fresh device result. Do not place extra orders. When present, use allowedIdentifiers and requirements to check identifier and brand compatibility. Missing values mean unknown; do not claim planned metadata is already available. Args: page: Page number (0-based). Defaults to 0. size: Number of services to return per page. Defaults to 200.

Submit IMEI or serial-number checks for one selected service using existing account credits. Supply serviceId, batchName, identifier strings in imeis, and notify. Preserve leading zeros. Before calling this tool, trim whitespace and remove blanks and duplicates within the current request/service; previous orders do not block an intentional new check. Order only within the user's requested scope and authorization, using a currently compatible service and price. Set notify false unless requested. Acceptance is not completion: use list_orders/list_batches to check actual orders and progress. Reconcile uncertain submissions before retrying; do not assume idempotency or equate unique input count with accepted orders. Successful orders are charged; failed orders are not. Do not equate acceptance with a charged success. The response reports submittedCount (total entries received), duplicatesRemoved (non-blank repeats), uniqueCount (distinct inputs), acceptedCount (orders actually created), rejectedCount (non-blank inputs the backend rejected), and rejectedInputs (each rejected identifier with its validation reason). Do not describe uniqueCount or submittedCount as the number of devices checked; use acceptedCount for created orders. Args: serviceId: The service ID to order (obtained from list_services). batchName: A human-readable name for this batch. imeis: List of IMEI or serial numbers to check (duplicates removed automatically). notify: Whether to send a completion notification.