ScorpTech x402 API

Resistor Network

resistor_network

Read-onlyIdempotent

Series or parallel equivalent of 2 to 24 resistances. Series adds them. Parallel is the reciprocal of the sum of the reciprocals. Exact rationals. Every value must be positive. One block only: a mixed ladder is not a mode. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/resistor-network

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": {
      "mode": "<mode>",
      "values": "<values>"
    },
    "name": "resistor_network"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	Yes
`values`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing cost ($0.001 USDC per successful call via x402 on Solana), an alternate HTTPS endpoint, the exact-rational output property, and the positivity precondition. These are operational facts an agent cannot get from readOnlyHint/idempotentHint.

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?

Front-loaded with what it computes and how, then constraints, then pricing. The terse fragment style is dense and nearly waste-free, though the two formula sentences could be compressed and the pricing/endpoint tail is slightly long.

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?

No output schema exists, so the description should imply the return shape; 'Exact rationals' suggests it but never states that the equivalent resistance is returned or in what format. Everything else an agent needs to call it correctly (bounds, positivity, mode enum, cost) is present.

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 0%, so the description must carry the load, and it does for mode (enum values defined with formulas) and the positivity constraint on values. It leaves the string encoding of values (e.g. '1/3' vs '0.5') unexplained despite the maxLength 40 hint, so not a 5.

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?

States a specific verb and resource ('series or parallel equivalent of 2 to 24 resistances') and even gives the mathematical definition of each mode. An agent can distinguish this from resistor_code, led_resistor, or voltage_divider without opening the schema.

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?

'One block only: a mixed ladder is not a mode' explicitly excludes a tempting but unsupported interpretation, which is real routing guidance. It stops short of naming which sibling to use for related tasks (e.g. voltage_divider for ladders), so it gets a 4 rather than a 5.

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?