Skip to main content
Glama
Sign In

ScorpTech x402 API

by com.it.scorptech
OverviewDiscussionsAdmin

Figi Validate

figi_validate
Read-onlyIdempotent

FIGI check digit. Twelve characters with no vowels. The first two are letters and are not BS, BM, GG, GB or VG, and the third character is G. The check uses the full A–Z alphabet, weights 1 and 2 from the left. Spaces are ignored. This does not call OpenFIGI. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/figi-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": "figi_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that validation is local and does not call OpenFIGI, that spaces are ignored, and that successful calls cost $0.001 USDC via x402 on Solana. It also provides the equivalent HTTPS endpoint. These are meaningful behavioral and cost traits that an agent would not know from annotations alone.

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 but front-loaded with the core validation concept, and each sentence carries relevant format, cost, or endpoint information. It could be slightly more structured with an explicit leading verb, but there is little waste.

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 single-parameter read-only validation tool with no output schema, the description covers the input format, payment behavior, and external-call behavior well. The main remaining gap is that it does not explicitly state the return value or result shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden. It does so by specifying the twelve-character FIGI structure, vowel restriction, allowed letter pairs, required third character G, full A-Z check alphabet, weighting scheme, and space handling.

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 identifies the resource as a FIGI and the operation as check-digit validation, with specific format rules that distinguish it from generic validators. However, it opens with a noun phrase rather than a clear verb, so the purpose is clear but not perfectly stated.

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?

It notes that this does not call OpenFIGI, which implicitly scopes the tool to local check-digit validation rather than issuer lookup. It does not explicitly say when to use this versus other validation tools or what the prerequisite input conditions are beyond the format rules.

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 toolsInspect
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