ScorpTech x402 Tools

Eui64

eui64

Read-onlyIdempotent

Modified EUI-64 from RFC 4291. A 48-bit MAC is expanded by flipping the U/L bit and inserting FF-FE in the middle. A 64-bit value with FF-FE in the middle is folded back to the MAC. Any other 64-bit value is returned as-is with mac null. The bits, local and multicast fields describe the 64-bit result. Flipping the bit makes a universal MAC look local in the interface id. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/eui64

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": "eui64"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond annotations that already mark it read-only and idempotent, the description explains the deterministic bit-level transformation, the pass-through behavior for non-EUI64 64-bit values, the mac null result, the meaning of bits/local/multicast output fields, and the pricing model. That is substantial behavioral context an agent would not otherwise have.

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?

The core transformation is front-loaded in the first sentence, followed by handling rules, result-field semantics, and then cost/endpoint details. Every sentence adds operational value with no filler.

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?

With no output schema, the description adequately describes returned fields (mac, bits, local, multicast) and the null case. For a one-parameter conversion tool it is close to complete, though it omits accepted input syntax and any error/validation behavior.

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

Parameters3/5

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

Schema description coverage is 0%, so the schema only says 'value' is a string with maxLength 40. The description compensates by explaining that the parameter may be a 48-bit MAC or a 64-bit value, but it does not specify the accepted input notation (e.g., colon-separated hex, bare hex, or decimal), which leaves a meaningful gap.

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 states a precise transformation: Modified EUI-64 per RFC 4291, including MAC-to-EUI64 expansion and EUI64-to-MAC folding. It is clear what resource is being converted, but it never names sibling tools such as mac_address or mac_local, so differentiation is left to inference.

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 accepted input cases imply when the tool applies (a 48-bit MAC is expanded, a 64-bit value with FF-FE is folded back, other values pass through). However, there is no explicit when-to-use guidance, no exclusion conditions, and no named alternative such as mac_address or mac_local.

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?