ScorpTech x402 API

Sl2 Trace

sl2_trace

Read-onlyIdempotent

The trace a+d of a 2 by 2 integer matrix [a, b, c, d]. The trace of [1, 1, 0, 1] is 2, and the trace of [8, 5, 5, 3] is 11. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/sl2-trace

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": {
      "matrix": "<matrix>"
    },
    "name": "sl2_trace"
  }
}

Input Schema

Name	Required	Description	Default
`matrix`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond the annotations: a per-call price ($0.001 USDC via x402 on Solana) and an alternative HTTPS endpoint. It stops short of stating error behavior for malformed arrays (e.g., fewer than 4 elements, since minItems is unset).

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 the definition and formula, followed by confirming examples, then payment and transport details. Every sentence adds information; only the redundant repetition of the word 'trace' in the examples is minor filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, read-only arithmetic tool with no output schema, the description supplies everything needed: the formula, the expected 4-element input layout, example inputs with their expected scalar outputs, and the cost/transport terms. Nothing material for correct invocation is missing.

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 description coverage is 0% and the single parameter 'matrix' is an untyped-semantics array of integers, so the description carries the burden. It does so well by defining the flat layout as [a, b, c, d] of a 2x2 matrix and showing two concrete input/output examples, removing ambiguity about ordering. It does not clarify what happens with fewer than 4 items or values outside the +/-1,000,000 bound.

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 gives an exact operation and formula: 'the trace a+d of a 2 by 2 integer matrix [a, b, c, d]', which unambiguously separates it from siblings like sl2_det or sl2_mul. It does not explicitly name those siblings, but the formula itself does the disambiguating work.

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?

Worked examples ([1,1,0,1] -> 2, [8,5,5,3] -> 11) confirm the intended semantics and input ordering, so usage is implied clearly. However, there is no explicit when-to-use/when-not guidance and no mention of the sibling SL2 tools (sl2_det, sl2_inv, sl2_pow) an agent would choose between.

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?