ScorpTech x402 Tools

Resistor Code

resistor_code

Read-onlyIdempotent

IEC 60062 resistor color code. Decode 3 to 6 bands, or encode a resistance that lands exactly on a digit-and-multiplier value. Digits run black=0 through white=9. Multipliers run from silver (×0.01) and gold (×0.1) through white (×1e9). Tolerances: brown 1%, red 2%, green 0.5%, blue 0.25%, violet 0.1%, grey 0.05%, gold 5%, silver 10%. Three bands mean 20% and have no tolerance band. The sixth band is the temperature coefficient in ppm/K: black 250, brown 100, red 50, orange 15, yellow 25, green 20, blue 10, violet 5, grey 1. Grey may be spelled gray. This does not measure a part. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/resistor-code

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resistor_code"
  }
}

Input Schema

Name	Required	Description
`ohms`	No	Resistance to encode. Exact decimal or a fraction such as 47/10.
`bands`	No	Colors, commas or spaces. Omit to encode ohms instead.
`count`	No	Bands when encoding. Default 4. Three bands are 20%.
`tempco`	No	ppm/K. Required for 6 bands, and only then.
`tolerance`	No	Percent when encoding: 0.05, 0.1, 0.25, 0.5, 1, 2, 5, 10, or 20. Default 5% for 4 bands, 1% for 5 or 6, 20% for 3.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely non-obvious behavior: it is a paid call ($0.001 USDC per successful call via x402 on Solana) and has an equivalent HTTPS endpoint. That payment gate and the alternate transport are exactly the kind of facts an agent needs and cannot get from annotations. It stops short of saying what the response looks like.

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?

Purpose is front-loaded in the first clause, followed by reference tables that are dense but each carries lookup value an agent would otherwise guess wrong. Every sentence earns its place, though the packing of four lookup tables plus payment and endpoint detail into one paragraph makes it heavier than ideal to scan.

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 self-contained color-code converter with no output schema, the domain rules, band-count rules, valid tolerance and tempco values, and payment requirement are all covered. The one gap is return shape: nothing says whether a decode yields just a resistance or a full band breakdown, which an agent has no other source for.

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?

Schema coverage is 100%, so baseline would be 3, but the description adds meaning the schema lacks: color-to-digit mapping (black=0 to white=9), the multiplier range including silver ×0.01 and gold ×0.1, the color-to-percent tolerance table, and the color-to-ppm/K tempco table. It also states that three bands mean 20% with no tolerance band. Only the ohms fraction format and count defaults are left to the schema.

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?

Opens with a specific standard, verb and resource ('IEC 60062 resistor color code. Decode 3 to 6 bands, or encode a resistance'), so the agent immediately knows this is a color-code converter in both directions. It does not name the near siblings (led_resistor, resistor_network, ohm_law, e_series), but the line 'This does not measure a part' does carve out the main confusion.

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?

States both operating modes (decode bands, encode a resistance that lands exactly on a digit-and-multiplier value) and an explicit when-not ('This does not measure a part'). The 'lands exactly on a digit-and-multiplier value' caveat is a real usage constraint. What's missing is any named alternative for the related circuit 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?