ScorpTech x402 Tools

Imei Validate

imei_validate

Read-onlyIdempotent

IMEI and IMEISV. A 15-digit IMEI must pass the Luhn check. A 14-digit IMEI has no check digit, and a 16-digit IMEISV has none either. Spaces and hyphens are ignored. This does not look the number up with a manufacturer. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/imei-validate

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": {
      "value": "<value>"
    },
    "name": "imei_validate"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds valuable operational context beyond annotations: the $0.001 USDC per successful call pricing, x402/Solana payment detail, HTTPS alternative endpoint, and the explicit 'does not look the number up with a manufacturer' limitation.

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?

The description is front-loaded with format rules and remains compact overall. Pricing and endpoint details are relevant for a paid API but make the final sentence operationally dense; the content still earns its place without significant waste.

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 a simple validation tool, the description covers purpose, accepted input formats, behavioral limitations, pricing, and an alternate endpoint. It does not explain the return value (e.g., boolean or details), but with no output schema and given the tool's simplicity, this is a minor gap rather than a blocking omission.

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?

Although schema description coverage is 0%, the description compensates by explaining the accepted input forms: 14-digit IMEI, 15-digit IMEI with Luhn check, 16-digit IMEISV, and that spaces and hyphens are ignored. This gives the agent sufficient semantic meaning for the single 'value' parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource ('IMEI and IMEISV') and the validation behavior via the Luhn check for 15-digit values. It distinguishes itself from a manufacturer lookup, but does not explicitly differentiate from the close sibling meid_validate, so it falls short of a 5.

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 provides input-format rules (14, 15, 16-digit forms, spaces/hyphens ignored), which implies when the tool is applicable. However, it gives no explicit when-to-use/when-not-to-use guidance or alternatives, such as clarifying when to prefer meid_validate or other validation tools.

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

All ScorpTech x402 Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?