ScorpTech x402 Tools

Isin Validate

isin_validate

Read-onlyIdempotent

ISIN check digit (ISO 6166). Two letters, nine letters or digits, one check digit. Letters expand to their alphabet position (A = 10) and the Luhn sum of that digit string must be 0. The prefix must be an ISO country code or one of the substitute prefixes EU, QS, QT, XA, XB, XC, XD, XF, XK, XS. Spaces are ignored. The national security id inside is not looked up. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/isin-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": "isin_validate"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, but the description adds substantive context: payment cost per successful call, x402/Solana billing, an HTTPS alternative, ignored spaces, and that the national security id is not looked up. It still omits rate limits and return behavior.

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 description is dense and front-loads the ISIN check-digit definition, followed by format and prefix details. Payment and endpoint information are useful but make it longer than a minimal validator description; still, each clause adds operational context.

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?

For a one-parameter validator with annotations and no output schema, the input format and algorithm are well covered. However, it never describes what the tool returns (boolean, error details, normalized ISIN) or how failures are represented, which matters because there is no output schema.

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?

There is one required parameter with 0% schema description coverage, so the description must carry the meaning. It does so by specifying the 12-character ISIN layout, letter expansion, Luhn check, allowed prefixes, and space handling, though it does not explicitly name the 'value' argument.

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 names ISIN and ISO 6166 and details the exact check-digit structure, so the resource is unambiguous. It does not explicitly contrast with other identifier validators, but the ISIN-specific format makes the purpose clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains validation rules but never states when to call this tool versus other validate_* siblings or when not to use it. There is no explicit guidance on input prerequisites or error handling.

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?