ScorpTech x402 API

Meid Validate

meid_validate

Read-onlyIdempotent

MEID, the CDMA equipment id. Hex is 14 digits with an optional Luhn check in base 16. Decimal is 18 digits (manufacturer and serial) with an optional decimal Luhn check, and it converts to the hex form. A 14-digit hex number that is only decimal digits is an IMEI, not a MEID. Spaces and hyphens are ignored. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/meid-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": "meid_validate"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantial context: optional Luhn checks, decimal-to-hex conversion, ignored spaces/hyphens, and pricing. It does not disclose what a successful validation response contains, which is a meaningful gap for a validator without an output schema.

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 format rules are front-loaded and the paragraph is dense with useful information. The pricing and HTTPS endpoint details are relevant but add bulk that is not strictly needed for tool selection.

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?

It covers the single input parameter and the MEID format rules well, which is important given 0% schema coverage. But with no output schema, the description should explain what validation returns—boolean, normalized value, Luhn status, or converted hex—and it never does.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the input semantics, and it does: it explains the two accepted formats, digit counts, optional Luhn behavior, ignored separators, and the IMEI ambiguity. This meaningfully compensates for the bare schema.

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 identifies MEID as the CDMA equipment id and specifies the accepted hex/decimal structures. It also explicitly distinguishes a decimal-only 14-digit hex string as an IMEI rather than a MEID, which helps the agent separate this tool from the sibling imei_validate.

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?

Usage is clearly implied for MEID validation, and the IMEI distinction gives useful routing guidance away from this tool. However, it does not explicitly name imei_validate as the alternative or state when not to call this tool beyond that format distinction.

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

All ScorpTech x402 API 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?