ScorpTech x402 Tools

Lei Validate

lei_validate

Read-onlyIdempotent

LEI check digits, ISO 17442 with ISO 7064 mod 97-10. Twenty letters or digits, and the whole number is 1 mod 97. Spaces and hyphens are ignored. This does not look the entity up at GLEIF. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/lei-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": "lei_validate"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantive extra context: the $0.001 USDC per-successful-call x402/Solana payment model, an HTTPS endpoint equivalent, and the no-lookup scope. It omits the failure/return behavior (e.g. whether invalid input returns false vs. error), which is the main remaining gap.

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?

Four short sentences, front-loaded with the validation rule, then scope exclusion, then pricing/endpoint. No filler and nothing redundant with the annotations.

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 would ideally say what a result looks like (boolean validity, error on malformed input). Everything else an agent needs — input format, scope, cost, transport — is present and accurate.

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 burden, and it does: the single 'value' parameter is described as 20 letters/digits with spaces and hyphens tolerated, which explains why maxLength is 40 in the schema. It adds real meaning beyond the bare string type.

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 (validate) and resource (LEI check digits) and pins the standard: ISO 17442 with ISO 7064 mod 97-10. It also draws an explicit boundary against the look-up interpretation ('This does not look the entity up at GLEIF'), so an agent can distinguish it from entity-lookup tools.

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?

Gives the acceptance rule (20 alphanumerics, whole number 1 mod 97, spaces/hyphens ignored) and an explicit when-not ('does not look the entity up at GLEIF'). It does not name a sibling alternative or say when to prefer e.g. a sanctions/GLEIF lookup, so it stops short of full routing guidance.

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?